Teams Meeting Link Formatting

Copper Contributor

Hello, 

 

When I send over a meeting invite from Outlook or the Teams app, the formatting goes wrong. It sends the invite to recipients as the picture attached. 

 

Has anyone run into this? Using this on a Mac. 

3 Replies

@ppgrootens 

 

Hi - did you get anywhere on this? We've started seeing it on Windows 10 devices and I'm at a loss.

 

The mail formatting is in HTML, the Teams plugin is operational and loaded.

 

Thoroughly confused thus far.

@ppgrootens 

We had the same issue that was only affecting a small sub set of users.   We finally pinpointed the issue and resolved it so hopefully this may help others.  

 

For us, it was related to an Office Policy that someone created for testing purposes.  They applied to an O365 group of about 10 users (few members of IT).   When we looked in the policies prior there was nothing as they had applied the policy, applied some of the recommendations, and later deleted the policy.   Although the policy was deleted the settings were still applied to these users M365 apps and thus causing the Meeting link formatting issue.  Also, it was causing these users issue with the FindTime add-in and presenting them with an error that it 'could not insert find time where cursor was'.  

 

If you login to Office Cloud Policy Service - Apps Admin Center, you can see if any policies exist.  In our case none did but we were able to create a new one and apply to the same group. 

 

When we did this, it brought back all the prior security recommendations that were applied.  

 

We went through each one and told it to revoke the setting, thus having no policies applied.  

 

Once the workstations synced, the users had to close all Office apps, relaunch and it fixed both the Teams meeting add-in formatting and the FindTime issue.  

 

Hopefully this is helpful to others.  

@DougBartley 

 

Oh very interesting, I'll need to wade through it - one thing immediately leaps out that as we're very very small we only have one policy for all users, and yet this issue isn't affecting everyone - but it's certainly worth the dive and I'll get back to you if I find anything that helps!