MIP Sensitivity Labels on GCC-High

And of course my case was closed without being resolved. Thanks Adobe! Great customer service. I'm so glad that I pay for a service that does not do what it says it'll do.  
ADB-41378993-K6N7

Has there been any resolution to this issue? We are experiencing the same issue.

@Nick27188053awkk Even though you're using Acrobat 2025, it appears the application is still requesting an older redirect URI (likely a legacy one from Acrobat 2021) for its authentication flow, and your Azure AD tenant for Adobe Acrobat (identified by the application ID 97bd680b-f203-4917-a342-308a3de4094a) doesn't recognize it. The bMIPExternalAuthAdmin registry key toggles different authentication methods, but it won't magically add a missing redirect URI to your Azure AD configuration. To resolve this, the solution lies squarely within your Azure Active Directory (AAD) portal, specifically within the Enterprise Application associated with Adobe Acrobat (ID 97bd680b-f203-4917-a342-308a3de4094a). You, or your Azure AD administrator, must log into the Azure portal, navigate to that specific Enterprise Application, and add acrobat2021.oauth2://miplogin as a valid "Redirect URI" for that application's authentication configuration. This tells Azure AD that it's safe to send authentication responses back to that specific URI when Acrobat initiates a login request. Once this URI is added and saved in Azure, Acrobat's authentication should succeed.