Converse agora com nosso suporte
Chat com o suporte

On Demand Global Settings Current - User Guide

Working with On Demand Overview of On Demand Signing up for On Demand Managing organizations and regions Adding users to an organization Managing your Azure tenants and on-premises domains On Demand Home page Settings Documentation roadmap Technical Support

Managing admin consent permissions

Once you add a tenant, you are redirected to a page that lists the permissions that will be granted. You must click Accept and provide admin consent for the On Demand application. Once the Global Administrator adds a tenant to On Demand, an application record is created in the tenant indicating that admin consent has been provided.

For security, when you first add a tenant, only the minimum permission settings are granted. Some modules require additional permissions for specific activities. Once a tenant has been added to On Demand, you can grant additional permissions on the Tenant Consents page.

On May 19, 2022, On Demand introduced a new consent experience using Microsoft Authentication Library (MSAL) which required that consent be regranted for modules that use delegated permissions. For details about MSAL, see About the Microsoft Authentication Library (MSAL) .

To open the Tenant Consents page, click Tenants in the navigation page and click Edit Consents on the tenant tile.

You can view the specific permissions for each On Demand application by clicking View Details. You can also see the last time that consent was granted and which On Demand user granted the consent.

About admin consent status

On the Tenant Consents page, you can view the module admin consent status for each tenant that you have added. The process of approving the use of an application for the Microsoft Azure AD organization by the Microsoft Global administrator is referred to as admin consent. A Microsoft Global administrator must provide admin consent when granting consents to any application listed on the page.

When a tenant is first added, On Demand requests base admin consent permissions. Some modules can function using the base permission set while other require a higher level of admin consent permissions.

When you grant consent in On Demand, a service principal is created in your tenant. Some On Demand modules require that a role be assigned to the service principal. The role is needed to support specific module functionality. For example, after granting consent for the Exchange Online PowerShell consent type, you must assign the Exchange Admin Role. This role is needed to perform Exchange tasks such as linking mailboxes to users and deleting mail-enabled groups.

Granting and regranting admin consent

You must grant specific admin consents for each On Demand tenant. For example, if you grant access for MyCompany tenant in organization A, and add the MyCompany tenant to organization B, you must grant consent for organization B. In some situations, you might have to regrant consent for an application used by your tenant.

For some consent types, you might also have to assign a role after you grant consent.

Click Tenants in the navigation panel on the left.
If the current status is Not Granted, you can enable the module consent type for this tenant by clicking Grant Consent.
If the current status is Regrant Consent, a change in the required permissions or new functionality might mean that you must regrant consent for a previously granted consent.

For the following scenarios, you would click Grant Consent or Regrant Consent in the Status and Actions column.

The admin consent token for the module expired, resulting is a status of Consent Required. The status of Consent Required indicates that On Demand cannot obtain a token with delegated permissions based on a previously granted admin consent. To restore the interrupted services, you must regrant consent.
A new feature in an On Demand module can require that additional permissions be granted. In this scenario, you would click Regrant Consent. For example, when On Demand implemented the new Microsoft Authentication Library (MSAL) in June 2022, admin consents had to be regranted for modules that use delegated permissions.
Admin consent has been revoked in the Azure AD portal, resulting in a status of Revoked. If you revoke the Core Basic admin consent in the tenant you will see Revoked status for Core Basic and Not Available for all other modules. The Core Basic application is used to determine the consent status for your tenant. If that consent is revoked, On Demand cannot determine consent status for the rest of the modules. Consent might be granted for the modules, but On Demand cannot verify it.

The Microsoft Authentication Library (MSAL) is the recommended library that replaces the deprecated Azure Active Directory Authentication Library (ADAL). MSAL provides improved security, is resilient, and allows tokens to be generated with a very granular scope. Since MSAL supports generated tokens with a granular scope, On Demand can use tokens with a narrowed scope when accessing your tenant.

This feature provides a more secure and granular approach for accessing your data. For more information, see Permissions and consent in the Microsoft identity platform.

For the License Management module, to use Self Server License Reporting, you must grant additional permissions over the Base permissions.

Sometimes, when you grant consent for Self Service License Reporting, you might see an error that indicates that the app requires access to a service that your organization has not subscribed to or enabled. This error occurs if the Microsoft M365 License Manager API, required to gather self-service policy data, is not enabled in the tenant by default. You can resolve the error by enabling the M365 License Manager API in the tenant.

Install the Azure PowerShell Az module if it is not already installed.

After you complete these steps, you can complete the Grant Consent for Self Service License Reporting without errors.

About revoking admin consent

Completely revoking admin consent removes all permissions granted for the On Demand application. Revoking admin consent is a manual process that must be performed in the Microsoft Azure portal.

NOTE: You can revoke or disable consent in the Microsoft Azure Portal.

Revoking admin consent removes all permissions granted for the On Demand application.

Click on the Azure Active Directory icon in the left menu.
At the top of the Properties pane, select Delete, and then select Yes to confirm you want to delete the application from your Azure AD tenant.

Alternately, to disable consent, you can disable a user from signing in.

Search for and select Azure Active Directory.
Select Enterprise applications.
Select Properties.
Select No for Enabled for users to sign-in?.
Select Save.
Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação