MC1528007 - Join button will require HTTPS meeting links

Microsoft 365 Message Center announcement MC1528007.

MS Message Center's Summary

Microsoft is updating Outlook to display the join button only for meetings with secure links starting late November 2026. Meetings with insecure links will not show the button. Administrators should verify that internal tools and third party meeting providers generate secure links before the rollout concludes in late December 2026.

Administrator impact
Review third party meeting providers and custom integrations to ensure they generate secure meeting URLs.
End user impact
Users will not see the join button in Outlook for meetings that use insecure links.
Importance
4/10: This change requires proactive verification of third party meeting integrations to prevent missing join buttons.

Microsoft Summary

Starting late November 2026, Outlook's Join button will only appear for meetings with HTTPS join URLs. Meetings with HTTP-only URLs will not show the button. Organizations should ensure their meeting providers and integrations generate HTTPS links to avoid impact. No action is needed if HTTPS URLs are already used.

Message Center ID
MC1528007
Category
plan For Change
Severity
normal
Services
Exchange Online
Tags
Feature update, Admin impact
Published
2026-10-27
Last updated
2026-10-27
Expires
2027-02-28

[What and Why:] We're updating the Join button experience in Outlook to use HTTPS meeting join URLs. Beginning the week of November 30, 2026, the Join button will no longer appear for meetings that contain only an HTTP join URL. [Rollout Schedule:] General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out in late November 2026 and expect to complete by late December 2026. [Impact on Your Organization:] Meetings with HTTPS join URLs will continue to display the Join button. Organizations using online meeting providers, add-ins, or custom integrations that generate HTTP-only join URLs may find that the button no longer appears for those meetings. Most organizations are not expected to be affected. [Action Required/Recommendations:] No action is needed if your meeting providers and integrations already generate HTTPS join URLs. If you use third-party online meeting providers, add-ins, or custom integrations, confirm that they generate HTTPS join URLs. Work with the provider or integration owner to update HTTP URLs and validate newly created meeting invitations before the change takes effect. [Compliance considerations:] No compliance considerations identified. Review as appropriate for your organization.