Skip to content

Ulysses Neves

Microsoft Entra ID, authentication, and hybrid identity troubleshooting.

Menu
  • Home
  • Microsoft Azure
  • Microsoft AD FS
  • Microsoft 365
  • Contact
  • Troubleshooting Index
Menu

Microsoft Entra Privileged Identity Management (PIM) – Monitoring Privileged Access with Alerts and Event History

Posted on October 15, 2019

Hello everyone. In today’s article, we’ll show you how to monitor requests and grants of privileged access using alerts and events in PIM. This article covers the “monitor privileged access” topic of the AZ-500 – Microsoft Azure Security Technologies exam. If you’re preparing to take this exam, don’t miss the upcoming articles on this blog.

Default alerts

Alerts are generated by Azure when there is some group access activity or suspicious activity in the environment. Let’s check the alerts generated in the environment in the next steps.

Checking alerts

If you haven’t yet enabled PIM on your Azure account, follow the steps in this link.

Access the Azure AD Roles menu in PIM through this link.

Sign in with your Azure credential.

Click Alerts.

Click Scan Now.

Let’s select the Roles are being assigned outsite of PIM alert.

Azure shows us the credentials that received privileged access without using PIM and the tool’s access grant control.

Let’s dismiss this alert by selecting the user Joseph and clicking Dismiss.

Now select the There are too many global administrators alert. This alert monitors the number of global administrators in Azure and flags when there are too many and a review is needed.

Let’s assume that the user Mantova no longer needs Global Admin access, and remove them from this role by clicking Fix selected.

The Potential stale accounts in a privileged role alert shows us the privileged accounts that haven’t had their passwords changed recently. It’s possible to identify and remove such accounts from the roles.

Configuring the default alerts

Now that we’ve identified the possibilities of Azure PIM alerts, let’s change some of the available parameters and show how to customize these alerts according to the company’s needs.

Access the Microsoft Entra ID role groups menu by clicking this link.

Click Settings and select Alerts.

Let’s change the Administrators aren’t using their privileged roles alert.

Click the alert you want to change.

Let’s change the amount of time a user can go without activating a role before it triggers a monitoring alert to 21 days.

Fill in the field with the number of days and click Save.

Click Save.

Directory role audit history

Another monitoring tool that can be used with PIM is Directory roles audit history, which lets us view privileged access activations graphically and in summary form. You can filter the view by time, action, and role, and export the chart data to a .csv file.

The My audit history menu shows the access grant activity of the user currently signed in to the Azure portal.

Summary
In today’s article, we showed how to monitor requests and grants of access to privileged groups managed by PIM using alerts and events.

With this article, we’ve wrapped up the subtopics related to the “Configure Microsoft Azure AD Privileged Identity Management” topic of the AZ-500 exam.

In the upcoming articles, we’ll cover the “Configure Microsoft Azure Active Directory for workloads” topic, starting with the subject of “how to configure MFA (Multi-factor Authentication) in Azure”.

I hope this content has contributed to enriching your knowledge of Azure.

Did you like the post? Like and share it. 🙂

If you have any suggestions or comments, let us know.

[ ]’s

Ulysses Neves

Related guides: Browse the Microsoft Identity Troubleshooting Index or the Microsoft Entra ID topic archive.

Leave a Reply Cancel reply

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

Recent Posts

  • Microsoft Defender for Identity domain investigation: six questions to ask first September 10, 2026
  • Microsoft Entra Kerberos key rotation: what changes—and what administrators should check September 6, 2026
  • Microsoft Authenticator Will Block Jailbroken Devices in 2026 — What You Need to Know March 17, 2026
  • Enhancing Azure role activation security with FIDO2/Passkeys September 23, 2024
  • Microsoft Entra ID CAP | Enforcing WHfB using Authentication Strength April 21, 2024

Archives

  • September 2026
  • March 2026
  • September 2024
  • April 2024
  • February 2024
  • December 2023
  • September 2023
  • July 2023
  • June 2023
  • May 2023
  • April 2023
  • March 2023
  • February 2023
  • January 2023
  • December 2022
  • October 2022
  • September 2022
  • August 2022
  • July 2022
  • June 2022
  • May 2022
  • April 2022
  • March 2022
  • February 2022
  • January 2022
  • December 2021
  • November 2021
  • October 2021
  • September 2021
  • August 2021
  • July 2021
  • June 2021
  • May 2021
  • April 2021
  • March 2021
  • February 2021
  • January 2021
  • December 2020
  • November 2020
  • October 2020
  • September 2020
  • August 2020
  • July 2020
  • June 2020
  • May 2020
  • April 2020
  • March 2020
  • February 2020
  • January 2020
  • December 2019
  • November 2019
  • October 2019
  • September 2019
  • August 2019
  • July 2019

Tags

#aaddownleveldevice #adfs #adfscertificate #adfscertificates #adfsmfaadapter #azureauth #azureCA #azuredevice #capolicy #cloudsummit2021 #conditionalaccess #conditionalaccesspolicy #deviceregistration #farmbehavior #gopasswordless #mfaserver #msidentity #namedlocation #securingazure #securingazuread #sslprivatekey #troubleshootingadfs #troubleshootingwaptrust #tshootadfs #waptrust #webapplicationproxy #WHFBcerttrust #whfbdeployment #WHfBhybridsetup #WHfBprovisioning #widdatabase adconnect AD FS authenticationstrength az500 azurepim Azure security cloudsecurity microsoft365 Microsoft Azure Microsoft Entra hybrid join Microsoft Entra ID Microsoft Entra MFA PowerShell WHfB
©2026 Ulysses Neves | Design: Newspaperly WordPress Theme
Ulysses Neves
Gerenciar Consentimento de Cookies
Para fornecer as melhores experiências, usamos tecnologias como cookies para armazenar e/ou acessar informações do dispositivo. O consentimento para essas tecnologias nos permitirá processar dados como comportamento de navegação ou IDs exclusivos neste site. Não consentir ou retirar o consentimento pode afetar negativamente certos recursos e funções.
Funcional Always active
O armazenamento ou acesso técnico é estritamente necessário para a finalidade legítima de permitir a utilização de um serviço específico explicitamente solicitado pelo assinante ou utilizador, ou com a finalidade exclusiva de efetuar a transmissão de uma comunicação através de uma rede de comunicações eletrónicas.
Preferências
O armazenamento ou acesso técnico é necessário para o propósito legítimo de armazenar preferências que não são solicitadas pelo assinante ou usuário.
Estatísticas
O armazenamento ou acesso técnico que é usado exclusivamente para fins estatísticos. O armazenamento técnico ou acesso que é usado exclusivamente para fins estatísticos anônimos. Sem uma intimação, conformidade voluntária por parte de seu provedor de serviços de Internet ou registros adicionais de terceiros, as informações armazenadas ou recuperadas apenas para esse fim geralmente não podem ser usadas para identificá-lo.
Marketing
O armazenamento ou acesso técnico é necessário para criar perfis de usuário para enviar publicidade ou para rastrear o usuário em um site ou em vários sites para fins de marketing semelhantes.
  • Manage options
  • Manage services
  • Manage {vendor_count} vendors
  • Read more about these purposes
Ver preferências
  • {title}
  • {title}
  • {title}