Microsoft 365 authentication failures affected Nylas Sandbox applications in the US and EU regions that used Nylas-provided shared credentials, caused by an expired credential that prevented new account connections and reauthentication. Production applications and Sandbox apps using their own Azure credentials were unaffected throughout the ~14-day incident. Resolution involved deploying updated credentials and an automated bulk update, with any grants that became invalid during the incident requiring manual reauthentication via the Nylas Dashboard.
Trusted by 1,000+ teams
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
The automated credential update has been successfully completed for affected Microsoft / Office 365 Sandbox applications in both the US and EU regions.
Microsoft authentication using Nylas-provided shared credentials has been restored. No manual credential updates are required.
Important: Any Microsoft grants that became invalid during the incident will still require reauthentication through your application's normal Hosted Authentication flow. You can identify these accounts in the Nylas Dashboard under Grants by filtering for Provider = Microsoft and Status = Invalid. Existing valid grants require no action.
Production applications and applications using their own Microsoft Azure credentials were not affected.
Thank you for your patience while we worked to resolve this issue. If you require additional assistance, please contact support@nylas.com.
Mitigated - The fix for Microsoft / Office 365 authentication failures affecting Sandbox applications using Nylas-provided shared credentials remains available.
Affected customers can restore authentication by following the instructions in our previous update. Step 1 (Update your Sandbox credentials) should be completed regardless of the additional automated remediation described below. Any Microsoft grants that became invalid will still require reauthentication.
We have successfully completed testing of an additional automated credential update, which is planned for Monday, October 26, to further address affected existing Sandbox applications.
If you are still experiencing authentication issues, please follow the instructions in our previous update or contact support@nylas.com for assistance.
Production applications and applications using their own Microsoft Azure credentials remain unaffected.
We will provide a final update once the remaining remediation work is complete.
Mitigated - We have deployed a fix for Microsoft / Office 365 authentication failures affecting Sandbox applications using Nylas-provided shared credentials.
Affected customers can now restore authentication using the following steps:
Step 1: Update your Sandbox credentials
1. Sign in to the Nylas Dashboard at https://dashboard.nylas.com.
2. Open your affected Sandbox application.
3. On the Overview or Connectors page, locate the expired Microsoft credential warning and click Update credential.
4. Confirm that the green "Microsoft credential updated" message appears.
If you do not see the warning banner, navigate to Connectors, select your Microsoft connector, and save it without making any changes. This will also apply the updated credentials.
Step 2: Reauthenticate affected Microsoft accounts (if needed)
1. Click View invalid Microsoft grants in the confirmation banner, or navigate to Grants and filter by Provider = Microsoft and Status = Invalid.
2. Reauthenticate any invalid grants using your application's normal Hosted Authentication flow.
Existing valid connections do not require reauthentication, and new Microsoft accounts can connect normally once the credentials are updated.
Additional remediation underway: We are also testing an automated bulk update for existing Sandbox applications to reduce the need for manual credential updates. Any grants that became invalid will still require reauthentication.
Production applications and applications using their own Microsoft Azure credentials remain unaffected.
We will provide a final update once the remaining remediation work is complete.
Deployment of the fix for existing affected Sandbox applications is progressing, and our Engineering team is now completing final testing and validation.
Once testing is complete, we will provide additional instructions for affected customers, including any steps required to restore Microsoft authentication.
Production applications and applications using their own Microsoft Azure credentials remain unaffected.
We have identified an expired credential affecting Microsoft / Office 365 authentication for Sandbox applications using Nylas-provided shared credentials.
Updated credentials have been deployed for newly created Sandbox applications, and we are now deploying a fix for existing affected Sandbox applications. Once available, affected users may need to refresh their credentials in the Nylas Dashboard and re-authenticate any impacted Microsoft accounts.
This issue is limited to Sandbox applications using Nylas shared Microsoft credentials. Production applications and applications using their own Microsoft Azure credentials are not affected.
We will provide another update as the fix is rolled out.
We have identified an expired credential affecting Microsoft / Office 365 authentication for Sandbox applications using Nylas-provided shared credentials.
Replacement credentials have been deployed for newly created Sandbox applications. Our Engineering team is continuing work to restore authentication functionality for existing Sandbox applications that may still be affected.
Production applications, applications using their own Microsoft Azure credentials, and existing active connections remain unaffected.
We will provide additional updates as remediation progresses.
We are investigating Microsoft / Office 365 authentication failures affecting Sandbox applications in the US and EU regions that use Nylas-provided shared credentials.
Affected users may encounter errors when connecting new Microsoft accounts or re-authenticating existing accounts.
Production applications, Sandbox applications using their own Microsoft Azure credentials, and existing active connections are not affected.
Our Engineering team is actively working to restore normal authentication functionality.
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with