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

AD FS – Monitoring AD FS with the Microsoft Entra Connect Health Agent for AD FS

Posted on May 8, 2020

Hello everyone. In today’s article we’ll show you how to install the Microsoft Entra Connect Health Agent for AD FS and monitor the environment through the Azure portal.

What is Microsoft Entra Connect Health for AD FS

Microsoft Entra Connect Health monitors the identity infrastructure by presenting incident alerts and security best practices, helping administrators maintain and ensure the environment is running properly. To make this monitoring possible, collection agents installed on the servers are used. All the information collected by the agents across the AD SYNC, AD FS, AD FS proxy, and AD DS infrastructure is displayed through the Health and Analytics portal, available through this link.

Installing the Microsoft Entra Connect agent for AD FS

Let’s download the agent by accessing the Health and Analytics menu mentioned above and clicking Download Azure AD Connect Health Agent for AD FS.

To properly monitor the AD FS environment, the agent must be installed on all AD FS servers and also on the proxy/WAP servers.

Let’s run the installer we downloaded.

Click install.

Click Configure Now.

When you run the step above, the installer opens a PowerShell window and you’re prompted for the user to perform the configuration. I’ll use an account with global administrator privileges, which by default has permission to register an agent in Azure.

Once authentication is complete, you can see that the agent registration finished successfully.

If you get a result similar to the one shown below, you’ll need to verify that all the installation requirements have been correctly met. For more information, go to this link.

With the agent installed, we can confirm that the services are functional.

Enabling auditing on the AD FS servers

Now let’s enable auditing on the AD FS servers. This step should not be performed on the AD FS proxy/WAP servers.

On the AD FS server, let’s open Server Manager > Tools > Local Security Policy.

Under Security Settings > Local Policies > User Rights Assignment, let’s double-click the Generate security audits setting.

Let’s add the AD FS service account in the window below.

Let’s run the command below at the Windows prompt to define the types of events to be monitored:

auditpol.exe /set /subcategory:{0CCE9222-69AE-11D9-BED3-505054503030} /failure:enable /success:enable

By accessing the AD FS > Edit Federation Services Properties… service, you can see that the Success audits and Failure audits events are enabled.

Validating the AD FS agents in the Azure portal

To validate that the installed agents are communicating with Microsoft Entra ID, go to this link. You can see the registered agents and their respective statuses, as shown below:

By selecting the agent, you can see some additional information about the AD FS environment.

Summary

In today’s article, we showed how to monitor the AD FS environment using the Microsoft Entra Connect Health Agent for AD FS. We explained step by step how to install it, register the agent, and validate the data in the Azure portal.

I hope this content has contributed to enriching your knowledge of Microsoft Entra ID.

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 AD FS 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}