Table of Contents
Use Share to Teams to post a Conversation from Outlook to Teams
Message center notification MC238648 published on February 9 said that Microsoft would update the Share to Teams feature. The update dutifully appeared on schedule during the last week of March. This feature is covered by Microsoft 365 roadmap items 71265, 70598, and 68909 because it is available in Outlook for Windows (Microsoft 365 apps for enterprise – March monthly channel), OWA, and Outlook for Mac (preview). The feature is not yet available for Outlook mobile.
The idea behind Share to Teams is simple. People receive a lot of email that they would like to discuss with colleagues. They could conduct the discussion in email with the known downsides of interminable series of to-and-fro replies, not all of which might be circulated to the same people. Taking the discussion to Teams keeps focus and makes sure that everyone sees the discussion developing and can contribute as needed.
Share to Teams Target Destinations
Launched in 2020, Share to Teams uses the same email connector infrastructure used to support the ability to send email to a channel. This is a connector which uses cloud-only mailboxes to accept inbound email addressed to channels and deliver them to Teams. In the case of Share to Teams, the addressee can be:
- A person (the message is delivered to a personal chat). The sender must be able to send a message to the person (information barrier policies can block people communicating via chat).
- A group chat: If you share a message from Outlook to multiple users, Teams delivers the message to the group chat involving those users (if one exists) or otherwise creates a new group chat.
- Any channel that the sender can access, including private channels. You cannot share to multiple channels at one time.
In all cases, messages can be sent with attachments.
Figure 1 shows a typical example. In this instance, we’re sharing a message from Outlook to a Teams channel.
Figure 2 shows what the shared message looks like in Teams. As you can see, it looks like any other base note for a conversation. Replies can be posted as normal. The only jarring note is that Teams does not highlight the subject of the conversation to make the topic stand out better in a list of topics.
You must be signed into your home tenant to be able to post messages to Teams. If you’re signed in as a guest to another tenant, Teams will tell you that you need to switch before it can post.
Capturing Message Copies in SharePoint Online and OneDrive for Business
Apart from messages delivered to target destinations, like email sent to channels, a copy of the shared message (including attachments) is captured in the Email Messages folder in the channel folder in the document library of the SharePoint Online team site. This is the way that the email connector used to behave until February 2021. Now, messages sent to a channel go into a folder named for the month, like EmailMessages_4_2021 for messages sent in April 2021. The change in target folder annoyed many people because it broke some Flows, and inconsistency like this drives people up the wall across Teams is maddening.
Copies of messages shared with individuals or group chats are in the Microsoft Teams Chat Files folder of the sender’s OneDrive for Business account.
No Protected Email
You can’t select the Share to Teams option for messages protected with sensitivity labels, the standard Outlook Encrypt-Only or Do Not Forward options, or S/MIME. This is because the connector cannot remove the encryption which protects these messages.
What’s Changed
When you share an Outlook message to Teams, the add-in checks for the presence of the Teams desktop client. If it’s available, the add-in uses single sign-on (SSO) to launch a new window in the Teams client to compose the message details for sharing. This is the major difference between the old method and the new. Creating a window in an already connected Teams client is faster and creates less overhead than the alternative, which is for Outlook to do the work to connect to Teams and send the message.
Admin Control
Microsoft says that Share to Teams is controllable “by selectively enabling or disabling this add-in for individual users via PowerShell Cmdlet. Admin documentation will be published soon.” Although Microsoft is promising that a cmdlet will be available, I’m not sure if many tenants will want to disable Share to Teams. It’s not a function that I used often, but I am grateful that it’s there when I need it. I suspect most other organizations will be in the same category.
This refresh won’t make much difference to users. It’s a improvement in software engineering that will bypass most, but that’s not a reason to ignore the development and update a paragraph in the Office 365 for IT Pros eBook. It’s what we do.
Finally! I can stop explaining to users why is this “Share to Teams” button grayed out 🙂 But all 3 roadmap entries are still “in development”. How fitting 😀 Btw, for some reason was not able to share to a few private channels (not appearing in search), but could in another private channel. Don’t see what is the difference. And what do you mean about subject not being highlighted? It is in bold and has envelop icon besides it. Or do you mean the text that you add as a description when sharing?
I mean the bolded topic name that you can add (and should add) to new conversations… You’re referring to the bolded message subject embedded in the text of the topic.
Btw, one user has updated to 2103 version of Office and still doesn’t see this new Share to Teams button. So it might not be just Office update. It might also depend on a feature enabled in Teams. But as features usually don’t depend on version number, there is no easy way to confirm that. When i saw new share button in Outlook i have also noticed that in Teams i now have two separate menus at the top for Settings (…) and for Profile/status (my picture). So, maybe this is some sort of indication when new share button should also appear in Teams.
The feature depends on the Teams meeting add-in. That’s the core component. https://office365itpros.com/2021/01/08/teams-meetings-addin/ I am running version 1.0.21063.3
Are you sure? I don’t think this button is part of Teams Meetings. i don’t have this add-in in my Outlook (we use Zoom for meetings0 and Share to Teams button works.
Check whether the add-in is loaded… I believe that the functionality is in the add-in. At least, that’s what Microsoft told me. And it’s the only code component Teams has to influence how Outlook (and OWA) work.
How do you check if it is loaded? I don’t see anything related to Teams add-in in Outlook, Task manager, Registry. Teams meetings is blocked on the org level, we can’t create them in Teams client, and probably add-in install is also blocked (i am not in the team controlling that). I now think that maybe old version of sharing button depended on Teams Meetings add-in and this is why it was always grayed out for us, because add-in was missing. But this new version probably doesn’t depend on that anymore. Maybe you can test this by disabling meeting add-in in your Outlook and checking if you can still share emails.
I played around with the add-in (which is loaded automatically at startup). It seems like disabling the add-in doesn’t remove the option, so what I was told needs some further investigation. I’ve removed the assertion in the text.
I have the button but it only works in webmail. If I try it in the outlook app it keeps saying “You need to switch to the (my email) account in Teams to share.” But I am signed into teams. So strange
It looks as if you are not signed into Teams in your home tenant. If you are not, Share to Teams doesn’t work.
Hi Tony, Yes I am signed into my only account.
Then it’s a bug. Report it to Microsoft and see what they say.
JP, I have the same exact problem as you. Did you figure out a solution?
Same issue with me
And are you signed into your home tenant or switched into another tenant. Try making sure that you are signed into your home tenant and then restart Outlook to see if that works.
It seems disabling Share to Teams can only be done on a per EXO Mailbox level and the Disable-App cmdlet does not accept pipelines. Does anyone know a clever way around this? Either using a variable or perhaps the Disable-App cmdlet is only able to be run once per user? My objective is to Disable Share to Teams for all users or a batch of users.
Something like this will work:
$AppId = “545d8236-721a-468f-85d8-254eca7cb0da”
[array]$Mbx = Get-ExoMailbox -Filter {CustomAttribute9 -eq ‘NoApp’}
ForEach ($M in $Mbx) {
Write-Host (“Disabling app for {0}” -f $M.displayName)
Disable-App -Identity $AppId -Mailbox $M.Alias -Confirm:$False
}
Thanks Tony – I’ll give it a test in our staging environment and let you know how it goes!
Remember to find a good filter to retrieve the mailboxes to update… I used customattribute9, but you could look for accounts belonging to a department, country, location, etc.
Im doing something dumb with the script input – any ideas (even without the filter)? I’m guessing the variable for $M needs to be defined or should I use an automatic variable if there is one for mailbox type?
$AppId = “545d8236-721a-468f-85d8-254eca7cb0da”
$Mbx = Get-ExoMailbox ForEach ($M in $Mbx) {Write-Host (“Disabling app for {0}” -f $M.displayName) Disable-App -Identity $AppId -Mailbox $M.Alias -Confirm:$False}
ParserError:
Line |
1 | $Mbx = Get-ExoMailbox ForEach ($M in $Mbx) {Write-Host (“Disabling ap …
| ~~
| Unexpected token ‘in’ in expression or statement.
Separate out the line to get mailboxes from the For loop
Line 1: $MBX = Get-ExoMailbox
Line 2: ForEach ($M in $Mbx) {…
That worked beautifully! Thank you so much! 🙂
For completeness here is what I had to run (it was necessary to add brackets/parenthesis to Tony’s script):
$AppId = “545d8236-721a-468f-85d8-254eca7cb0da”
$Mbx = Get-ExoMailbox
ForEach ($M in $Mbx) {Write-Host (“Disabling app for {0}” -f $M.displayName) (Disable-App -Identity $AppId -Mailbox $M.Alias -Confirm:$False)}