Microsoft Exchange Admin Center Issue Blocks Web Portal Access to Admins With “Internal Server Error”

Blog WriterCybersecurity News - Original News Source is cybersecuritynews.com


Microsoft is investigating an Exchange admin center access issue that may prevent some administrators from opening the web portal used to manage Exchange Online. Affected admins may encounter an “Internal Server Error” message, according to the Microsoft 365 Status update provided for this report.

The company is tracking the incident under EX1500900 and has directed customers to the Microsoft 365 admin center for further information. The notice describes an access problem affecting some admins. It does not establish a global outage or confirm that users are unable to send and receive email.

“We’re investigating an issue in which some admins may be unable to access the Exchange admin center (EAC) and may encounter an ‘Internal Server Error’ message,” the supplied notice states.

Exchange Admin Center Issue

The Exchange admin center is Microsoft’s web-based console for managing Exchange Online. IT teams use it to manage mailboxes and groups, review mail flow reports, and handle migrations. Microsoft’s Exchange admin center documentation explains that available features depend on the administrator’s assigned roles and permissions.

Losing access can delay these tasks, particularly when teams need to review delivery problems or make urgent mailbox changes. However, an unavailable management portal does not, by itself, show that the underlying email service has stopped working. The supplied incident notice identifies admin access as the reported problem.

The brief announcement does not identify a root cause, affected regions, the number of impacted organizations, or a recovery timeline. It also does not announce a confirmed workaround. Those gaps mean the incident should not be described as a cyberattack or linked to a specific service change.

Administrators should check Health > Service health in the Microsoft 365 admin center and look for EX1500900. Microsoft’s service health guidance explains that this dashboard lists active incidents and advisories, with individual pages providing further details about each issue.

The Microsoft 365 Admin mobile app also supports service health updates and push notifications. This gives teams another way to follow Microsoft’s investigation without relying on the Exchange management interface itself. Updates should be checked against the incident record rather than inferred from reports about unrelated outages.

For essential work, Exchange Online PowerShell provides a separate command-line management interface. It supports Exchange Online administration, including security features. However, Microsoft’s supplied notice does not confirm that PowerShell is unaffected, so it should be treated as a possible alternative rather than a verified workaround.

Cybersecurity News previously covered a Microsoft Exchange admin center outage tracked as EX1051697. That incident involved HTTP 500 errors and reports of an alternative portal address helping some administrators. Those earlier findings do not establish a working fix for EX1500900.

The publication also reported a separate Exchange Online disruption tracked as EX1464935, which concerned broader service functionality. Its different incident number and reported impact underline why administrators should keep individual service events separate when assessing business disruption.

For now, the supported scope remains limited to the access failure described in the supplied announcement. Organizations should follow EX1500900 for confirmed impact, recovery progress, and any approved mitigation. Email delivery failures, if observed, need separate verification rather than being automatically attributed to this admin portal issue.

Cut every SOC alert investigation by 21 min. Power your SOC with instant IOC context for immediate response: Integrate TI Lookup into your SOC

The post Microsoft Exchange Admin Center Issue Blocks Web Portal Access to Admins With “Internal Server Error” appeared first on Cyber Security News.