We have identified the root cause of the disruption affecting Copilot Coding Agent and Issues. Copilot @-mentions on pull requests are not being processed, and some issue-related functionality may be degraded. A fix has been developed and is being applied.
Last update on
Fabric customers may experience issues receiving Fabric artifact share email notifications. Only the email notification is affected, artifact sharing is working as intended within the service. Engineers are investigating and updates will be provided soon. Power BI has reenabled external email send functionality for limited set of customers on a case-by-case basis. If your tenant is still impacted and wish to request re-enablement, please generate a support request for assistance.A mitigation is in validation phases and the tenant level switch for external recipients should be respected again by 2026-05-01 17:00 PDT.
Last update on
We are providing an update on the ongoing service disruptions affecting the AWS Middle East (Bahrain) Region (ME-SOUTH-1). We continue to make progress on recovery efforts across multiple workstreams. With the immediate phase of this event now better understood, we are moving to a more targeted communication model. Going forward, updates will be delivered directly to affected customers through the AWS Personal Health Dashboard. Customers who require assistance with this event are encouraged to contact AWS Support through the AWS Management Console or the AWS Support Center. We continue to strongly recommend that customers with workloads running in the Middle East take action now to migrate those workloads to alternate AWS Regions. Customers should enact their disaster recovery plans, recover from remote backups stored in other Regions, and update their applications to direct traffic away from the affected Regions. For customers requiring guidance on alternate regions, we recommend considering AWS Regions in the United States, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements.
Last update on
Our engineers have corrected the issue and we are confirming that the latest extension release has been approved. The fastest way to ensure you are running the latest version is to manually update your LastPass browser extension. We will continue monitoring the situation and provide a final update shortly.
Last update on
Our engineers are continuing to investigate the issue with the Design Editor preventing module movement. Initial findings suggest Chrome's latest update (ver.147) from last Wednesday may be the cause. For the best experience, please use the latest version of Safari or Firefox while we work on a fix. We will provide another update in 2 hours or as soon as more information becomes available.
Last update on
Core Cloud Services - Zscaler Client Connector: Zscaler detected an issue where the existing access token that was generated before April 11, 2026 can not be used to deploy Zscaler Client Connector for VDI. As a workaround customers can create a new access token while the Zscaler team investigates and fixes the issue. We will continue to provide updates here as the investigation progresses. Status changes and additional details will be posted there as they become available.Customer Impact: Customers won’t be able to deploy Zscaler Client Connector for VDI using existing access tokens that were created before April 11 (administrators generate access tokens in the Cloud and Branch Connector portal under Administration > VDI Templates). Administrators will receive "Init Config error" once they try to deploy Zscaler Client Connector for VDI with an existing access token.Customers running non-persistent VDI deployments and do not have a backup restore mechanism implemented to restore user profiles and config files stored in %programdata%/ZCCVDI. In this case, the agent must re-enroll on every boot using the access token from the golden image. If the golden image contains an access token generated before April 11, every boot will fail with "Init Config error" until the golden image is updated with a new token. Already-enrolled agents in persistent environments are not affected, as they do not need to re-enroll.Workaround: Generate a new access token from the Cloud and Branch Connector portal (Administration > VDI Templates) and use the new token for any new deploymentsFor non-persistent VDI where no user backup/restore was implemented: Update the golden/master image with the new access token, this is critical since the agent re-enrolls on every boot.
Last update on
Monitors
Power BI customers in North Europe and EastUS2 regions may experience delays in refreshing the models in the service. Engineers are investigating the issue and an update will be provided soon.
Microsoft Fabric
Increased Connectivity Issues and API Error Rates
Amazon Web Services
LastPass
SendGrid
Core Cloud Services - Zscaler Client Connector: Zscaler Client Connector for Virtual Desktop Infrastructure (VDI) Deployment Issue (+4 more)
Zscaler Cloud
StatusGator