Microsoft.com Displays Certificate Expiry Warning

Key Takeaways

• A critical Microsoft domain, connectivity.office.com, used by IT professionals for Microsoft 365 network diagnostics, began displaying untrusted connection warnings.
• The domain’s TLS certificate, issued by Microsoft Azure, expired on June 14, 2026, failing to be renewed after its six-month validity period.
• This lapse impacts automated diagnostic tools and scripts, potentially disrupting network health checks for organizations globally.
• The incident highlights a significant certificate management oversight, especially as Microsoft advocates for robust certificate hygiene among its enterprise customers.

Microsoft’s Connectivity Domain Flags Untrusted Connections Due to Expired Certificate

A significant oversight in Microsoft’s certificate management has led to a crucial domain, connectivity.office.com, generating untrusted connection warnings in web browsers since Monday. This domain is widely utilized by system administrators globally to verify Microsoft 365 connectivity and ensure network components like firewalls are not impeding essential services.

Expired Certificate Triggers Browser Warnings

The connectivity.office.com domain, a cornerstone tool for IT professionals diagnosing network issues related to Microsoft 365, is now presenting a NET::ERR_CERT_DATE_INVALID error in Chromium-based browsers. This error indicates that the security certificate presented by the server is no longer valid, prompting browsers to flag the connection as untrusted.

Upon inspection, the certificate, issued by “Microsoft Azure RSA TLS Issuing CA 07,” expired on Sunday, June 14, 2026, at 08:38:02 UTC. Records show the certificate was last renewed on December 16, 2025, providing a validity window of exactly six months. Microsoft evidently failed to renew this certificate before its expiration date.

Further examination of the certificate confirms ownership by Microsoft Corporation, with the TLS certificate possessing a SHA-256 fingerprint of c52ca2abaffcb192ef02ff7c131504d32b0311024c4ec7f8a439c44f17347baa. An SSL server report retrieved on Monday corroborated the lapse, explicitly stating the certificate was valid for 180 days before its unrenewed expiry. Browser warnings explicitly inform users: “This server could not prove that it is connectivity.office.com; its security certificate expired 2 days ago.”

Operational Impact and Contradictory Messaging

The connectivity.office.com domain serves a critical function, specifically designed to assist enterprise IT teams and network engineers in diagnosing Microsoft 365 connectivity problems. It helps identify whether network infrastructure such as firewalls, proxies, or other appliances are obstructing traffic to Microsoft servers. With the certificate now expired, browsers deem the site untrusted, which can cause automated tools or scripts reliant on HTTPS connections to this endpoint to fail silently or return certificate validation errors, thus disrupting crucial diagnostic workflows.

Organizations that integrate this endpoint into their network health checks or utilize it within onboarding verification scripts are directly affected by this issue. This incident is particularly noteworthy given Microsoft’s ongoing emphasis on robust certificate hygiene. The company has been actively advising enterprise customers to proactively renew older 2011-era Secure Boot certificates ahead of their own impending expiry between June and October 2026.

Allowing a publicly accessible, IT-critical domain’s TLS certificate to lapse directly contradicts Microsoft’s own guidance on certificate lifecycle management. Failures in this area are widely regarded as among the most preventable security misconfigurations, especially given the availability of automated renewal systems, which Microsoft itself promotes through Azure services, designed precisely to avert such lapses.

As of this report, Microsoft has not released an official statement regarding the expired certificate. However, given the operational visibility and importance of the affected domain, a prompt renewal of the certificate is anticipated.

What You Should Do

• Temporarily adjust automated scripts or diagnostic tools that rely on the connectivity.office.com endpoint to handle certificate validation errors gracefully or to bypass validation if deemed safe within a controlled diagnostic environment.
• Monitor official Microsoft channels for an announcement regarding the certificate renewal.
• If manually testing connectivity, be aware that browser warnings are legitimate and indicate an expired certificate, not necessarily a malicious compromise of the domain itself.
• Review internal certificate management practices to ensure similar lapses do not occur within your own infrastructure.

Disclaimer: HackersRadar reports on cybersecurity threats and incidents for informational and awareness purposes only. We do not engage in hacking activities, data exfiltration, or the hosting or distribution of stolen or leaked information. All content is based on publicly available sources.