For a third party app, like Boxer, to connect to Office 365, the app must be on the Azure enterprise app list. Otherwise, an app will be blocked from connecting.
To make it a seamless flow, Azure is by default to grant end user the right to authorize an app on the fly.
Once the app is approved to be an enterprise app by the first user, subsequent users do not have to give a consent anymore.
We have seen cases that users are blocked to do so. This stops users from starting using Boxer.
In case you run into similar scenario, you can review your consent setup and make it work again.
User will be promoted for permission request if it is the first time for Boxer to connect to your domain.
Boxer is added to enterprise app after user accept a request.
These are default consent settings on Azure which should allow user to grant permission to Boxer. If you see a difference and your Boxer is not added, please consider changing your consent setup.
Please note that this only happens when modern authentication is on. If an app is authenticated with basic authentication, getting the app to add to enterprise app list is not necessary.
This is a demo video on how Boxer is added to Enterprise App list when modern authentication is on. Boxer was first to connect using basic authentication and this did not trigger adding Boxer to the enterprise app list. When modern authentication was on, user was promoted to grant permission to allow Boxer to connect. User’s approval triggered Boxer to be added to the enterprise app list.
Comments