Client Credentials for Oauth 2.0 are expiring for Email Accounts, Oauth 2.0 Email is failing, Connection for Oauth email accounts stopped suddenlyIssue Test connection is suddenly failing on email accounts, email account utilizing O Auth 2.0 is no longer working or Client Credentials for Oauth 2.0 are expiring for Email Accounts.ReleaseAll EnvironmentsCauseClient Secret to acquire the token on Microsoft has a maximum expiration of 24 months, therefore the Client Secret will need to be renewed.ResolutionAccess the Application on the Microsoft Side and verify the Client Secret has Expired. Note: If this is not RCA, refer to KB0816072 If Client Secret has expired, create new client secret.On Application Registry, access Oauth associated with email accounts and update client secret.Go to Manage Tokens and delete tokens associated with the Oauth ProfileRepeat Step 6 from KB0816072 Use "Authorize Email Account Access" action to obtain the access and refresh token. You must use an incognito/private window and a local login (side_door.do if needed) to make sure your personal account is not picked up by Microsoft SSO login. The username/credentials of the email account should be provided, not your own credentials. If you try to authorize while you are already logged in to Azure, no pop-up window will appear and it might look like the authorization succeeded. However, the instance will receive an access token for your own credentials instead of the email account. Testing the connection will result in an error in this case since the instance will be using your account to access the mailbox and fail. (Note: The instance needs to have a valid/active Oauth token to use to connect to the mailbox in question (it be IMAP or SMTP) so that once the connection is established, the email data can be pushed to the mailbox in question: if you don't have one, go into the Oauth profile being used in the email account record and there should be a link for "Get Oauth Token" which you can click on to obtain a new token.