![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(108.80000000000001, 74%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMS%3C/text%3E%3C/svg%3E)
Azure Storage
Globally unique resources that provide access to data management services and serve as the parent namespace for the services.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(83.2, 52%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EVS%3C/text%3E%3C/svg%3E)
Hi Meghana Suresh,
Thanks for reaching out in Microsoft Q&A forum,
Observed intermittent Azure Storage impact in the East US region affecting a subset of services. Failures lasted approximately 2–3 minutes and recovered automatically.
Yeah, according to the Azure status,
Azure Service Health that confirms the multiple services issue in East US was mitigated, with the last update around 15:35 UTC on March 20.
Spotted those intermittent Azure Storage hiccups today in East US affecting just a subset of ops for 2–3 minutes each, auto-resolving as expected. Matches the broader degradation window (15:05–15:35 UTC) across services, now fully mitigated per the portal.
Steps:
- Grab the tracking ID from Service Health for your records or customer comms.
- Double-check logs in that UTC timeframe to close the loop on any residuals.
Kindly let us know if the above helps or you need further assistance on this issue.
Please do not forget to 
and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.