@oxize Thanks for reaching out. We're not tracking any issues that match your description. Please log a ticket with support or contact @MicrosoftHelps who may be able to assist you.
We've confirmed after monitoring our telemetry that the automatic scaling efforts to increase processing throughput were successful and the service has returned to healthy levels. For more information, see TM1526111 in the admin center.
We're investigating a potential issue for Microsoft Teams, affecting some users in the United States. For more information, see TM1526111 in the Microsoft 365 admin center.
We're beginning to observe restoration as our automated recovery actions take effect. We're monitoring to ensure full recovery, and in parallel, we're continuing to investigate the initial cause of impact. For more information, see TM1526111 in the admin center.
@AnggaAgia Thanks for reaching out. We're not tracking any issues that match your description. Please log a ticket with support or contact @MicrosoftHelps who may be able to assist you.
@NC_Languages Thanks for reaching out. We're not aware of any issues matching your description. Please log a support ticket or contact our friends @MicrosoftHelps.
@karthiksankar78 Thanks for reaching out. We're not tracking any issues that match your description. Please log a ticket with support or contact @MicrosoftHelps who may be able to assist you.
We've completed deploying the fix to the affected infrastructure and we've verified with previously impacted users that the issue is now resolved. For more information, please see CW1507178 in the admin center.
We're investigating an issue affecting model selection options in Copilot Chat. We're currently reviewing service telemetry to isolate the root cause and determine our next troubleshooting steps. For more information, please see CW1507178 in the admin center.
We've identified a component responsible for producing the model selection options in Copilot chat was not functioning correctly. We're deploying a fix to the affected infrastructure to mitigate impact. For more information, please see CW1507178 in the admin center.
Thanks for reaching out. We’re not aware of any current issues matching what you’ve described. If you continue to experience the issue, please close your current EAC browser session, open a new session, and try accessing the EAC again.
If the issue persists, please submit a support ticket or contact our friends @MicrosoftHelps for additional assistance.
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. For more information, please see EX1500900 in the admin center.
@jakob_davidson We've identified an issue in which similar symptoms have been reported. For more information, please see MO1505952 in the admin center, or visit https://t.co/uSHwRmXFJZ.
@jsummers71 We're investigating an issue with similar symptoms. For more information, please see MO1505952 in the admin center, or visit https://t.co/uSHwRmXFJZ.
@Casefort We're investigating an issue with similar symptoms reported. For more information, please see MO1505952 in the admin center, or visit https://t.co/uSHwRmXFJZ.
@TcA31252005 Thanks for reaching out. We're not tracking any issues that match your description. Please log a ticket with support or contact @MicrosoftHelps who may be able to assist you.
We’ve rolled back the change and confirmed through service telemetry and impacted users that the issue is now resolved. For more information, please see EX1500900 in the admin center or via https://t.co/5Stivwz7bm.
We’re rolling back a recent change to the Exchange Admin Center (EAC) to determine if this resolves the impact. While we're closely monitoring for improvement we're continuing to investigate the source of the issue. For more information, please see EX1500900 in the admin center or via https://t.co/v0BOp5U77c.