Let us learn about FIX – Error SCCM Azure AD Web App Already Exists. SCCM 1806 gives an option to deploy Cloud DP using Azure Resource Manager (ARM). However, I don’t recommend using cloud DP. Rather, you can use CMG to download content.
As SCCM is going through many co-management enhancements, we have to delete the Azure AD Web app and recreate it for testing purposes. This post will see issues related to Azure AD Web App Already Exists.
Content
What are Azure Services for Cloud Mgmt?
Issue – Azure AD Web App Already Exists Error
How to FIX Error Azure AD Web App Already Exists
What are Azure Services for Cloud Mgmt?
Deploying the Azure service for Cloud Management enables SCCM clients to authenticate with the site using Azure Active Directory. You can also allow the discovery of Azure Active Directory resources for this tenant.
I recommend reading How to create Azure services for a cloud management blog post to get more details. The above blog post will help you build Azure Service for cloud management from the SCCM console.
Azure AD Web Apps = Azure AD Server Apps
Issue – SCCM Azure AD Web App Already Exists Error
I hit an error while recreating the CMG (cloud Management Gateway). Even after deleting the existing Azure service created for Cloud Management, I could not create a new Azure Service for cloud management. I hit the below error:-
“An Azure AD Web app already exists for this tenant. Use the pre-existing app and click ok.”
Even though I have deleted the WEB APP in Azure for Authentication (Server App for SCCM) from the Azure portal, I was getting the above error. Let’s see what the quick fix to this issue is.
How to Fix Error Azure AD Web App Already Exists
I don’t recommend performing any SQL DB changes to fix this issue with the Azure AD web application. I think it’s better to resolve the problem from the SCCM console itself.
- Navigate to -> \Administration\Overview\Cloud Services\Azure Active Directory Tenants
- Select the Azure AD Tenant from the SCCM console List view
- Click on the DELETE button from the Ribbon menu to delete the tenant to ensure the Azuree apps and tenant are deleted.
- Now, recreate the applications using my previous post, How to create Azure services for cloud management.
Resources
SCCM 1806 New Features and Changes – https://www.anoopcnair.com/sccm-1806-new-features-video-walkthrough/
All Co-Management Video Tutorials in one post – https://www.anoopcnair.com/setup-co-management-video-tutorials/
Integrate Apps with Azure AD – https://docs.microsoft.com/en-gb/azure/active-directory/develop/quickstart-v1-integrate-apps-with-azure-ad
Hi Anoop,
On 1806, I’m not getting an option to delete the Applications themselves even though I have selected one. Instead, it’s only trying to delete the tenant. Not sure if you or anyone else knows of a workaround for this. I have a couple orphaned Applications under my tenant now.
Yes that is correct from AD Tenants node you won’t get an option delete the apps (Sorry – updated the post). I think you can delete the apps from Azure Services node? I’m not infront of console to confirm this.
Hi Anoop,
Thanks for getting back to me. It doesn’t look like the apps can be deleted from the Azure Services node either. When creating an Azure Service it looks like you can only create the tenet application. In my case, I hadn’t given my App Registration the correct privileges to the proper resource group, so my Azure Service didn’t populate everything properly. After exiting out of that wizard, that’s when the tenet apps got orphaned since they cannot be selected again.
Which version of SCCM .. Is it 1806?
Yeah 1806 with the first hotfix installed.
Do you think deletion of application from Azure AD will help? I recommend to delete the apps from both the places (Azure portal and SCCM) before recreating it.
I have deleted the app registrations from Azure AD. Didn’t have anywhere I could do the same in the SCCM console. I put in some feedback on this issue so hopefully someone from their team will follow up. According to the Ignite 2018 Chalk Talk session I attended, someone actually checks the feedback submitted.