When a login loop occurs after a sign-in attempt, it is usually due to an issue with the client secret provided in a policy's Identity settings.
If the client secret field is improperly configured, the resulting behavior is typically a black screen appearing after signing in via the Azure webview, followed by the webview reappearing.
The following remediations depend on whether the Azure app registration is a Web application or a Mobile and Desktop application (In the Azure portal, this can be viewed in Azure Active Directory >> App registrations >> [select an application] >> Authentication).
Azure Web applications
Confirm that the data provided in the policy's client secret field is the Value from Azure, and not the Secret ID. Since the Value is only shown once when the client secret is first created, it may be necessary to create a new client secret to get this key.
Azure Mobile and Desktop applications
If the Azure application is Mobile and Desktop, a client secret should not be added to the Addigy policy's Identity settings. If one is present, it should be removed.
Following this, deploy the policy and verify that the user is able to access their desktop after sign-in.