Lab2 Identity - Setting Up PIM
Lab2 Identity - Setting Up PIM
Want to learn more: What is Privileged Identity Management? - Azure AD | Microsoft Docs
Pre-requisites
Step 1 – Create Demo Tenant
Before you start you should have completed the “Getting started with Labs”. If you have not
completed this, you will not be able to do this lab. You can find this document which you can download
from https://aka.ms/secpractice-labs.
Each tenant can take up to 24 hours to provision so it’s important that you complete this prior to when
the labs are to be run.
Important: As a best practice in your real-world deployments, you should always write down the
first global admin account’s credentials (in this lab, the MOD Administrator) and store it away for
security reasons. This account is a non-personalized identity that owns the highest privileges possible
in a tenant. It is not MFA activated (because it is not personalized) and the password for this account
is typically shared among several users. Therefore, this first global admin is a perfect target for attacks,
so it is recommended to create personalized service admins and keep as few global admins as possible.
For those global admins that you do create, they should each be mapped to a single identity, and they
should each have MFA enforced.
5. In the Microsoft 365 admin center, in the left navigation pane, select Users and then
select Active users.
6. In the Active users list, you will see the default MOD Administrator account as well as
some other user accounts.
7. In the Active Users window, select Add a user.
8. In the Set up the basics window, enter the following information:
2. Click consent to PIM if it appears. In some tenants PIM is already enabled and therefore these
steps are unnecessary.
4. Click Next.
5. Enter your mobile/cell phone details and click Next.
6. Enter the code when you receive it via SMS and click Verify.
10. Back on the Consent to PIM blade click Consent and click Yes.
11. Refresh the Azure Portal by pressing F5.
Note: If by refreshing the portal in the browser does not display PIM as being enabled then log out
and back into the Azure Portal.
Part 1 – Complete.
Part 2 – Assign Directory Roles
Task 1: Make a user eligible for a role.
In the following task you will make a user eligible for an Azure AD directory role.
3. Select Roles. If this is option is still greyed you may need to refresh your browser.
4. Select Billing Administrator.
5. Select + Add assignments to open Select a member. In the Add assignments screen click No
member selected.
6. In the Select a member screen select Patti Fernandez and then click Select.
7. In Add assignments screen on the Setting tab unmark the Permanently eligible checkbox.
Click Assign. Review the added member in the assignment window.
8. When the role is assigned, the user you selected will appear in the members list as Eligible for
the role.
1. In the Azure Portal, click All services, and search for and select Azure AD Privileged
Identity Management.
Results: The Billing Administrator role is now listed as permanent for Patti Fernandez. In other
words, Patti is permanently eligible to be elevated to the Billing Administrator role.
1. In the Azure Portal, click All services and search for and select Azure AD Privileged
Identity Management.
Part 2 – Complete.
Part 3 – Activate and Deactivate PIM Roles
Task 1: Activate a role.
When you need to take on an Azure AD directory role, you can request activation by using the My
roles navigation option in PIM.
1. In the Azure Portal, signed-in as Global Admin, click All services and search for and
select Azure AD Privileged Identity Management.
4. Click Billing Administrator and add Patti Fernandez back into the Billing
Administrators role.
5. Open an In Private browsing session and navigate to https://portal.azure.com and login
as Patti using her UPN. example [email protected] with the
password given by your lab host (hint: the password is likely the same as the MOD
Administrator password).
6. In the Azure Portal, click All services, and search for and select Azure AD Privileged
Identity Management.
7. Click Azure AD roles.
8. Click Quick start and click Activate your role.
9. On the Billing Administrator role, scroll to the right and click Activate.
10. Click Verify your identity before proceeding if this appears here. You only have to
authenticate once per session. Run through the wizard to authenticate Patti.
11. Once returned to the Azure Portal, click All services and search for and select Azure AD
Privileged Identity Management.
12. Select Azure AD Roles then click click Activate your role on the Quick start blade.
13. On the Billing Administrator role, scroll to the right and click Activate.
If the role does not require approval, it is activated and added to the list of active roles. If you want to
use the role right away, follow the steps in the next section.
If the role requires approval to activate, a notification will appear in the upper right corner of your
browser informing you the request is pending approval.
1. Still signed in as Patti, in the Azure Portal, click All services and search for and select Azure
AD Privileged Identity Management.
2. Click Azure AD Roles.
3. Click Pending requests to see a list of your requests.
Task 4: Deactivate a role.
Once a role has been activated, it automatically deactivates when its time limit (eligible duration) is
reached.
If you complete your administrator tasks early, you can also deactivate a role manually in Azure AD
Privileged Identity Management.
Part 3 – Complete.
Part 4 – Directory Roles (General)
Task 1: Start an access review for Azure AD directory roles
in PIM.
Role assignments become "stale" when users have privileged access that they don't need anymore. In
order to reduce the risk associated with these stale role assignments, privileged role administrators
or global administrators should regularly create access reviews to ask admins to review the roles that
users have been given. This task covers the steps for starting an access review in Azure AD Privileged
Identity Management (PIM).
4. Once the review has completed and has a status of Active, click on the Global Admin
Review. You may need to refresh the view in Azure.
5. Select Results and see the outcome of Not reviewed.
Task 2: Approve or deny access.
When you approve or deny access, you are just telling the reviewer whether you still use this role or
not. Choose Approve if you want to stay in the role or Deny if you don't need the access anymore.
Your status won't change right away, until the reviewer applies the results. Follow these steps to find
and complete the access review:
3. Unless you created the review, you appear as the only user in the review. Select the check box
next to a user.
4. Close the Review Azure AD roles blade.
After the access review period is over, or all the users have finished their self-review, follow the steps
in this task to manage the review and see the results.
1. Go to the Azure portal and select the Azure AD Privileged Identity Management.
2. Select Azure AD Roles.
3. Select the Access reviews.
4. Select the Global Admin Review. Review the blade.
Part 4 – Complete.
Part 5 – PIM Resource Workflows
Task 1: Configure the Global Administrator role to require
approval.
1. You should still be logged in as Global Admin from the previous exercise. Open Azure AD
Privileged Identity Management.
2. Click Azure AD roles.
3. Click Settings
4. Select Global Administrator.
5. Click Edit, scroll down and mark Require Approval to activate.
6. Click Select approver(s) and assign Global Admin as the approver and click Select. Then
click Update.
Eventually you should see a notice that your request is "pending approval".
1. Switch back to the browser you are signed in with your Global Administrative account.
2. Open Azure AD Privileged Identity Management.
3. Click Approve requests.
Part 5 – Complete.
Part 6 – View audit history for Azure AD
roles in PIM
You can use the Azure Active Directory (Azure AD) Privileged Identity Management (PIM) audit history
to see all the role assignments and activations within the past 30 days for all privileged roles. If you
want to see the full audit history of activity in your directory, including administrator, end user, and
synchronization activity, you can use the Azure Active Directory security and activity reports.
End lab
Thank you for taking the time to complete this lab, we hope you enjoyed it.