Bobcares

How to set up Admin Consent Workflow in Azure Portal

by | Jun 10, 2024

Get ready to explore the many features of Admin Consent Workflow in Azure Portal with our experts. Our DevOps Support team is here to help you with your questions and concerns.

How to set up Admin Consent Workflow in Azure Portal

Managing app permissions in Azure can sometimes feel overwhelming. Fortunately, the admin consent workflow makes it easier for everyone involved. This feature lets users request access to applications that require more permissions than they currently have while giving administrators the power to grant or deny these requests securely.

Let’s break down how this process works and why it’s beneficial.

How the Admin Consent Workflow Works

  1. Imagine a user trying to access an application that requires admin-level permissions, like accessing sensitive user data. They see an “Approval required” message.
  2. The user has to then explain why they need the access and submit a request for admin approval.
  3. This request is then forwarded to designated reviewers—administrators with the right roles. They can view it in the Microsoft Entra admin center.

    The request includes details about the application, the permissions needed, and the user’s justification.

  4. At this point, reviewers can approve, deny, or block the request. The user gets to know about the decision via email.

Why the Admin Consent Workflow is a Game-Changer

  • All permission requests are managed in one place, streamlining the approval process.
  • Users provide explanations for their access needs, helping reviewers make informed decisions.
  • Controlling permissions at a granular level minimizes the risk of unauthorized access.

How to set up the Admin Consent Workflow

To enable the admin consent workflow, we need to be a Global Administrator. Here’s a step-by-step guide by our experts:

  1. First, log into the Microsoft Entra admin center as a Global Administrator.
  2. Then, go to Identity > Applications > Enterprise applications > Consent and permissions > Admin consent settings.
  3. Now, set “Users can request admin consent to apps they are unable to consent to” to Yes under Admin consent requests.

    admin consent workflow in the azure portal

  4. Next, select users, groups, or roles designated as reviewers. Reviewers can view, block, or deny requests, but only Global Administrators can approve requests for apps needing Microsoft Graph app roles.
  5. Furthermore, enable or disable email notifications for reviewers when a request is made or about to expire.
  6. Also, configure how long requests stay valid and set up reminders for reviewers.
  7. Finally, click save. It can take up to an hour for the workflow to be fully enabled.

Pro Tips for Smooth Configuration

  • Select the most appropriate reviewers who understand the application and its required permissions.
  • Ensure users know they need to provide a strong justification for their access requests.
  • Periodically review and adjust settings to ensure the process remains efficient and secure.

[Need assistance with a different issue? Our team is available 24/7.]

Conclusion

By following these steps, we can create a secure and efficient process for managing application permissions in Azure, ensuring that users get the access they need without compromising security.

In brief, our Support Experts demonstrated how to set up Admin Consent Workflow in Azure Portal and its many benefits.

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF