Application Permissions - Ensure the User Consent Workflow is Enabled

By Ashwin Venugopal -

 









Summary

If the admin consent workflow is not enabled, then, the user in a tenant will be blocked whenever they try to access any app that requires permissions to access organizational data. A generic error message will be seen saying that they are unauthorized to access the app and they should ask their admin for help.

Reason

This setup will offer a secure way to grant access to the applications requiring admin approval. Hence, when a user is unable to provide consent, they can send a request for admin approval via email to the admins designated as reviewers. A reviewer will act on the request, and the user will be notified of the action. 

What If?

In order to approve requests, a reviewer must be a global administrator, cloud application administrator, or application administrator, must already have one of these admin roles assigned; simply designating them as reviewer doesn't elevate their privileges.

How to?

To enable the admin consent workflow (Preview), use the Microsoft 365 Admin Center:
  1. Select Admin centers and Azure Active Directory.
  2. Select Enterprise Applications from the Azure navigation pane.
  3. Under Manage, pick Users settings.
  4. Now, set Users can request admin consent to apps they are unable to consent to, to Yes under Admin consent requests.
  5. Under the Reviewers, choose the Roles, Groups that you would like to review user generated app consent requests.
  6. Click the Save button at the top of the window.

Monitor:

To verify the admin consent workflow (Preview) is enabled, use the Microsoft 365 Admin Center:
  1. Select Admin centers and Azure Active Directory.
  2. Select Enterprise Applications from the Azure navigation pane.
  3. Under Manage, pick Users settings.
  4. Now, verify that Users can request admin consent to apps they are unable to consent to, is set to Yes.






























































Comments

Post a Comment

Popular posts from this blog

Deployment (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Microsoft Monitoring Agent (MMA) MMA is used across multiple Microsoft solutions and has undergone a few name changes as its features and functionality have evolved. If it is being considered to be used, then following areas should be covered during a Microsoft Sentinel deployment project: Consider the timelines and the strategy for a migration to AMA (Azure Monitor Agent) before the MMA end-of-life.  Consider the central deployment and management methodology for MMA. Determine which endpoints are in scope for deployment as these affect the log ingestion volume significantly.  Azure Monitor Agent (AMA) Organizations with MMA as the main Microsoft Sentinel agent should start planning the migration to AMA as soon as possible to avoid a rushed migration. One of the main advantages of AMA is the ability to control the log collection policy centrally and apply different policies against different...
Read more

Deployment (Part 1)

By Ashwin Venugopal -
Image
  To read part 2, please click  here To read part 3, please click  here Azure Resources Microsoft Sentinel needs following resources to be created: Subscription (if a dedicated subscription(s) will be used) Resource group(s) Log Analytics workspace(s) Automation rules/playbook Alert rules Workbooks Microsoft Sentinel offers hundreds of alert rules, workbooks, and automation playbook templates along with hunting scripts. The templates can be used to activate/deploy schedule alerts, create customized dashboards, create automation playbooks and perform threat-hunting activities. Generally, once deployed, the resources created have to be adjusted to match the existing environment, configure local credentials, etc. Methods of deployment: Manual- Administrator can manually configures the Microsoft Sentinel resources with the help of Azure portal. Any manual process has the inherent risks of human operator error, lack of compliance with potential change control procedures, and u...
Read more

Project Resourcing (Part 2)

By Ashwin Venugopal -
Image
  To read part 1, please click  here Engineering - SIEM The SIEM engineers configures Microsoft Sentinel, including Log Analytics, Logic Apps, workbooks, and playbooks. They are also responsible for the following high-level tasks: Initial configuration of Azure tenant, including provisioning required resources, assigning access roles, and configuring workspace parameters like log retention, resource tagging, and blueprints.  Deployment and configuration of syslog/CEF log collection agents in appropriate locations to collect logs from on-premises devices. Generally, it will be joint effort of both system engineer and SIEM engineer, involving configuration and potential troubleshooting.  Working with system owners to enable log forwarding and configuring any required parsing of log data in Log Analytics.  Working with security operations to create and deploy KQL analytic rules to offer detections for SOC/Computer Security Incident Response Team (CSRIT) use. Tuning...
Read more