Join my colleagues and me as we discuss a few topics that matter most to Microsoft 365 admins this month.
MC1486282 -- Update Teams devices to a minimum app version ahead of the retirement of Exchange Web Services (EWS)
Exchange Web Services (EWS) is being retired, and Microsoft Teams will feel the impact. A Teams degradation is often the symptom of a change elsewhere, and this change is no exception. The fix is relatively simple: keep your Teams applications up to date.
Desktops should follow the normal update lifecycle - make sure those monthly estate checks include Teams version checks. Not only on desktop - I'm looking at you, VDI!.
Teams rooms, panels and phones - With the move from Teams Admin Center (TAC) to Teams Room Pro Management Portal (PMP) now is a good opportunity to check those update rings are populated with the correct devices - pro tip: always have some devices in the staging ring (or create an earlier ring) for testing.
Mobile devices - these can be trickier to manage but equally important to maintain the latest versions.
There are various places to check the Teams app version in use:
- Teams Client Health (TCH) in Teams Admin Center helps identify Teams application versions that are not current.
- Pro Management Portal for your Teams Devices estate.
- PowerBI QER reports will show you teams version in use - but crucially only those used for meetings and calls.
- Usage reports in Teams Admin Center will give a more complete inventory of desktop and device usage.
- Intune may help manage your mobile/BYOD estate.
Happy updating!
Jonathan Christie
MC1530615 -- Microsoft Teams: Report Guest Invitations for Security Concerns
Next up is a new Microsoft Teams security feature, Report Guest Invitations for Security Concerns, which allows users to report suspicious invitations to join another organisation directly from Teams, helping IT administrators detect phishing attempts and guest invitation abuse.
Reporting suspicious invitations – When users receive an unexpected or potentially malicious invitation to join another organisation as a guest, they can report it as a security concern when declining the invitation. The report is shared with their IT administrator and Microsoft for review.
IT administrators – Reported invitations will appear in the User reported security submissions report in the Teams Admin Center. Security teams should ensure these reports are monitored and reviewed as part of their existing security processes.
Messaging policies – The feature is controlled by the existing Report a security concern setting in Teams messaging policies. If this setting is already enabled, no additional configuration is required. Otherwise, administrators should review the setting to determine whether to enable the capability.
The feature will roll out worldwide between early and mid-November 2026, covering Teams on Windows desktop, Mac and Web.
A few things worth checking:
- Review the Report a security concern setting in Teams Admin Center under Messaging policies.
- Ensure the appropriate teams monitor the User reported security submissions report.
- Inform users that suspicious guest invitations can be reported when declining them.
- Consider that reported invitations are shared with Microsoft for review, particularly where organisational data-handling requirements apply.
A useful addition to Teams security, particularly for organisations looking to improve visibility into potentially malicious guest invitations.
Happy Discovering!
José Lampreia
MC1485116 -- EWS restrictions enforced, but there is more to do before April 2027
EWS deprecation in Exchange Online began on 1 October. If you implemented EWSAllowedAppIDs and your apps survived, that's good news, but the job isn't finished. The question now is what needs to be done before 1 April 2027, when EWS is switched off permanently and admins can no longer turn it back on.
What's still coming:
- More tenants switched off: Tenants that didn’t change their EWS settings are being turned off in waves, each with a 7-day warning in Message Center. If you haven't had that post yet, assume it's coming.
- The allow list is now your inventory: Any tenant keeping EWS must list the apps allowed to use it. Each app on that list is a dependency that must move to Microsoft Graph before April 2027.
- Cross-tenant sharing: Free/busy, calendar and MailTips sharing with other Microsoft 365 tenants runs on EWS. Move it to cross-tenant access policy (MC1446796) before April 2027. Remember – it isn’t just your tenant that needs to be updated. You’ll need to work with the partner Microsoft 365 organization to ensure a seamless transition for your end users.
- Hybrid: Free/busy and MailTips between on-premises and cloud mailboxes will require Exchange Server SE using Microsoft Graph by April 2027. Exchange 2016 and 2019, which are both out of support, will permanently stop working in April 2027.
A few things worth planning now:
- Identify any Organization Relationships still in place. For those still required, work with the partner Microsoft 365 organization to get a cross-tenant access policy configuration in place. Top tip: Organization Relationships take priority over the cross-tenant access policy, so you can implement side by side and disable the Organization Relationship after you add the new policy. This allows for testing on your own schedule.
- Use this time as an opportunity to document each app on the allow list – find an owner, a vendor contact and communicate a date to move off EWS well ahead of the Microsoft timeline. Remind them this is the last chance – there will be no further exceptions after April 2027.
- Continue to check the EWS usage report over 90 days. If an app has migrated, remove it from the EWSAllowedAppID list.
- Plan a test switch-off before April, so you have plenty of time to work on any issues that arise.
- Check Microsoft Learn for a list of EWS features Microsoft Graph won't support.
- If your end users require Excel Power Query (AppID a672d62c-fc7b-4e81-a576-e60dc46e951d), they will need to manually update Excel workbooks when a new set of connectors is released. Please see https://aka.ms/xlewsretirement.
- For PowerBI (AppID b52893c8-bc2e-47fc-918b-77022b299bbc) our engineering teams will provide an update soon.
Happy migrating!
Antony Lincoln