Our workflows suddenly stopped working because the Authentication of the Outlook nodes have ceased functioning. When I tried reconnecting, it gave me the error Error: Client authentication failed (e.g., unknown client, no client authentication included, or unsupported authentication method).
Under more details (I hid the IDs in case they have sensitive information):
More details
{"error":"invalid_client","error_description":"AADSTS7000222: The provided client secret keys for app 'aad843ca-42a7-421xxxxxxxxxxxxx' are expired. Visit the Azure portal to create new keys for your app: https://aka.ms/NewClientSecret, or consider using certificate credentials for added security: https://aka.ms/certCreds. Trace ID: 6f408b68-8428-4dfd-9a42-a359e8800900 Correlation ID: ae81950e-2207-4ee0-a961-f036ac2f94b8 Timestamp: 2025-12-03 19:27:40Z","error_codes":[7000222],"timestamp":"2025-12-03 19:27:40Z","trace_id":"6f408b68-8428-4dfd-9a42-a359e8800900","correlation_id":"ae81950e-2207-4ee0-a961-f036ac2f94b8","error_uri":"https://login.microsoftonline.com/error?code=7000222"}
Failed to connect. The window can be closed now.
Now we’re stuck. All the workflows have stopped working. We tried reconnecting the account or even using another one but nothing gives.
ADSTS7000222: The provided client secret keys for app ‘…’ are expired. means that the client secret your n8n workflow is using to authenticate to Microsoft Graph (Outlook) has expired. This is not a problem with n8n itself, but with your Azure AD app registration. Generate a New Client Secret in Azure
Go to the Azure Portal App Registrations.
Select your app (the one with ID aad843ca-42a7-421xxxxxxxxxxxxx).
Go to Certificates & Secrets → Client secrets → New client secret.
Give it a description (e.g., n8n Dec 2025) and choose an expiration (1 year, 2 years, or custom).
Click Add.
Copy the value of the new secret immediately. Once you leave this page, you cannot retrieve it again.
Update n8n Credentials
In n8n, go to Credentials.
Find your Microsoft Outlook / Microsoft 365 account credentials.
Edit the credential:
Update the Client Secret with the new secret you just generated.
Make sure the Client ID and Tenant ID are correct.
Test the connection to ensure it works.
Note: If you have multiple workflows using this credential, updating the credential will fix all of them. TRY THIS HOPE IT HELPS
But I never setup a key, I only pressed “Connect with your account” button on the interface. When I pressed it again I got the above mentioned error (because it’s not working). This is most likely the client token of N8N with AZURE ?
Hence, the error mentioned above comes from N8N’s node, not from my side:
{"error":"invalid_client","error_description":"AADSTS7000222: The provided client secret keys for app 'aad843ca-42a7-421xxxxxxxxxxxxx' are expired. Visit the Azure portal to create new keys for your app: https://aka.ms/NewClientSecret, or consider using certificate credentials for added security: https://aka.ms/certCreds. Trace ID: 6f408b68-8428-4dfd-9a42-a359e8800900 Correlation ID: ae81950e-2207-4ee0-a961-f036ac2f94b8 Timestamp: 2025-12-03 19:27:40Z","error_codes":[7000222],"timestamp":"2025-12-03 19:27:40Z","trace_id":"6f408b68-8428-4dfd-9a42-a359e8800900","correlation_id":"ae81950e-2207-4ee0-a961-f036ac2f94b8","error_uri":"https://login.microsoftonline.com/error?code=7000222"}
Note: If you have multiple workflows using this credential, updating the credential will fix all of them. TRY THIS HOPE IT HELPS