Add better integration between ConfigMgr Cloud Services and Azure for removal of services and related items
If I delete my Azure Services and delete their corresponding components from my tenant, they still remain in the Applications pane of the Azure Active Directory Tenants node. Whenever I attempt to add the Azure Service back, like Could Management, it will give an error about the tenant already existing (which is confusing) which is telling me that the Application is already in my tenant (even if it has been deleted). So if I've already deleted the Application from my Azure tenant the wizard expects me to re-use it but it's no longer available to use. The fix has been to delete the entries from the DB, or completely remove ALL of the cloud services and then delete the Tenant altogether and start over - neither of which is great. Can you add an option to support the deletion of Applications from the tenant in the console or integrate it with ARM so that it deleted from the tenant when it is deleted from cloud services?
Jürgen Winter commented
The problem still persists with 2103 (Plus Rollup). There are old applications in our tenant according to the sccm console. The corresponding applications have long been deleted in Azure itself but there is no option to delete them on the sccm side. (Apart from removing all cloud services which are still active and removing the complete tenant from sccm and re-adding it from scratch).
Now i have permanent warnings and errors in the sccm console because of "expired secrets". A refresh is of course impossible since the Applications no longer exist on the Azure side.
Hello, I have same issue. Any info how fix the issue.