Admins couldn't download the Migration Manager agent from the SharePoint admin center.
- Status
- Wiederhergestellt
- Funktion
- SharePoint Online all features
- Region
- Nicht angegeben (alle Regionen)
- Beginn
- 02.11.2026, 10:07 Uhr
- Behoben
- 03.11.2026, 05:00 Uhr
- Dauer
- 18 Std. 53 Min.
Mehr Informationen
Admins received an error stating, "The specified container does not exist."
Betroffen
Your organization was affected by this event, and this issue prevented admins from downloading the Migration Manager agent.
Ursache
A storage account containing files required for application downloads was inadvertently disabled, which caused the removal of the files needed to execute the download and resulted in impact.
Next steps:
- We're reviewing our storage account file management procedures to help prevent similar problems in the future.
This is the final update for the event.
Abschluss
We've identified that a storage account containing files required for application downloads was inadvertently disabled, which caused the removal of the files needed to execute the download and resulted in impact. We've restored the affected files and confirmed that users can successfully download the applications again. We’re also progressing a long-term solution to prevent similar impact from recurring.
Verlauf
Alle Updates von Microsoft zu dieser Meldung, das neuste zuoberst.
- 03.11.2026, 14:17 Uhr
We've identified that a storage account containing files required for application downloads was inadvertently disabled, which caused the removal of the files needed to execute the download and resulted in impact. We've restored the affected files and confirmed that users can successfully download the applications again. We’re also progressing a long-term solution to prevent similar impact from recurring.
- 03.11.2026, 02:18 Uhr
We've identified a change to the SharePoint Online service that we believe is causing impact. We're in the process of rolling back this change and once complete, we'll validate whether it has had the desired effect of resolving impact.
- 02.11.2026, 21:59 Uhr
It's taking longer than expected to review the service telemetry and potential changes that may be contributing to this issue, but we're making progress as we strive to understand the root cause and devise a strategy that remediates impact.
- 02.11.2026, 19:48 Uhr
We're continuing to review the service telemetry and looking for potential changes that could be contributing to the issue to identify the root cause and a strategy that remediates impact.
- 02.11.2026, 17:42 Uhr
We're reviewing admin reports of impact and service telemetry for this functionality to gain a better understanding of what's leading to this behavior.
- 02.11.2026, 17:04 Uhr
We’re looking into your reported issue and checking for impact to your organization. We'll provide an update within one hour.
Störungen in LEXOJ abonnieren