Question
My organization’s System Center Configuration Manager (SCCM) version 2111 server Technical Preview lab (TP2101) displays the following message:
One or more Azure AD app secrets used by Cloud Services will expire soon. Renew to avoid service disruptions.
How do I resolve SCCM error “One or more Azure AD app secrets used by Cloud Services will expire soon. Renew to avoid service disruptions”?
Solution
According to Microsoft’s statement:
You need to renew the Azure AD app’s secret key before the end of its validity period. If you let the key expire, Configuration Manager can’t authenticate with Azure AD, which will cause your connected Azure services to stop working.
Starting in version 2006, the Configuration Manager console displays notifications for the following circumstances:
- One or more Azure AD app secret keys will expire soon
- One or more Azure AD app secret keys have expired
To mitigate both cases, renew the secret key.
For more information on how to interact with these notifications, see Configuration Manager console notifications.
Follow the below solution steps to resolve fix SCCM error “One or more Azure AD app secrets used by Cloud Services will expire soon. Renew to avoid service disruptions”:
Step 1: Click on the Renew secret link in the notification to reveal the Secret Key Expiry (UTC) dates.
Step 2: Right-click on the soon to be expired app.
Step 3: Select the Renew Secret Key option from the context menu.
Step 4: The Microsoft Azure sign in dialog box will prompt. Enter the credentials of either the app owner or an Azure AD administrator to sign in Microsoft Azure.
Note: If the sign in user is not app owner or Azure AD administrator role, error “Failed to renew the secret key for AAD server application. The remote server returned an error: (403) Forbidden.” will display.
Step 5: The new date is shown in the console.
Reference
Microsoft Docs > Enterprise Mobility + Security > Microsoft Endpoint Manager > Configuration Manager > Core infrastructure guide > Configure Azure services for use with Configuration Manager
