[GUEST ACCESS MODE: Data is scrambled or limited to provide examples. Make requests using your API key to unlock full data. Check https://lunarcrush.ai/auth for authentication information.]
@MSFT365Status
"We're currently investigating an issue impacting Please see our service health page for further details:" @MSFT365Status on X 2025-07-10 02:18:01 UTC 286.6K followers, 123.8K engagements
"@AntonyRunner Thank you for reaching out. Weve investigated and resolved the issue. You can track the status by referencing incident MO1120879 in the Microsoft XXX admin center. If you need further assistance please submit a support ticket or contact our team via @MicrosoftHelps" @MSFT365Status on X 2025-07-24 02:02:02 UTC 286.6K followers, XXX engagements
"Our automated recovery features have taken action to restore service; however we're still investigating the underlying cause of the impact. Please look for TM1112332 in the admin center for more updates" @MSFT365Status on X 2025-07-09 18:50:05 UTC 286.6K followers, 41.4K engagements
"@DevGerman Thank you for reaching out. Weve investigated and resolved the issue. You can track the status by referencing incident MO1120879 in the Microsoft XXX admin center. If you need further assistance please submit a support ticket or contact our team via @MicrosoftHelps" @MSFT365Status on X 2025-07-24 02:02:37 UTC 286.6K followers, XXX engagements
"We're investigating an issue where some users may be experiencing issues with Microsoft Teams. Please look for TM1112332 in the admin center for more updates" @MSFT365Status on X 2025-07-09 18:30:08 UTC 286.6K followers, 89.3K engagements
"Our service telemetry indicates full recovery for the issue affecting Microsoft Teams. Please look for TM1112332 in the admin center for more details" @MSFT365Status on X 2025-07-09 19:44:00 UTC 286.6K followers, 32.4K engagements
"We identified an issue with the initial fix and we've corrected it. We're continuing to deploy the fix and we're closely monitoring the deployment to ensure no further issues are encountered. Please visit for more information" @MSFT365Status on X 2025-07-10 13:20:35 UTC 286.6K followers, 28.2K engagements
"@ryguy287 Thank you for reaching out. Weve investigated and resolved the issue. You can track the status by referencing incident MO1120879 in the Microsoft XXX admin center. If you need further assistance please submit a support ticket or contact our team via @MicrosoftHelps" @MSFT365Status on X 2025-07-24 02:00:53 UTC 286.6K followers, XXX engagements