大网数据广告活动
域与目录服务

AD FS Troubleshooting - Microsoft Entra Connect Health Data

· 52CE 我爱测

Learn how to troubleshoot data freshness from the Microsoft Entra Connect Health agent for Active Directory Federation Services.

This article describes troubleshooting steps for the Microsoft Entra Connect Health for Active Directory Federation Services (AD FS) data freshness alert: "Health service data is not up to date."

Check if your AD FS security audits are enabled

You can configure AD FS to do service auditing of user sign-ins to reveal a level of detail. For the Usage Analytics feature to gather and analyze data, the Microsoft Entra Connect Health agent needs the information in the AD FS audit logs. These logs aren't enabled by default. On your AD FS servers, use the following procedures to enable auditing and to locate the audit logs. To check the status of AD FS security audits:

  1. Select Start, point to Administrative Tools, and then select Local Security Policy.
  2. Double-click Local Policies, and then select Audit Policy.
  3. On the details pane, double-click Audit object access.
  4. Check the status of the audit object policy on the Audit object access properties page.

Enable AD FS audit events

Depending on your machine settings, we have steps here to enable AD FS audit events:

Run Restart-Service AdHealth*

If you use AD FS on Windows Server 2016, make sure Verbose AuditLevel is set

Use these commands:

Set-AD FSProperties -AuditLevel Verbose

Run Restart-Service AdHealth*

Check for multiple service member entries in config.json

Go to C:\Program Files\Azure Ad Connect Health ADFS Agent\Insights\config.json. Open the file in a JSON editor or look for multiple instances of the string ServiceType: AdFederationService.

Look for runtime errors in the agent debug trace

  1. In the event viewer, enable analytic and debug logs.
  2. Find Applications and Service logs\ADHealth-AD FS\Debug.
  3. Right-click, increase the size to 100032, and enable the log. Disable and then reenable to clear.
  4. Restart the insight service by running Restart-Service AdHealth*.
  5. Wait for five minutes, and then refresh the log.
  6. Select Ctrl+F to find AgentType = Insights. Look for logs with error/authorization information.
  7. If errors look to be related to OAuth/token issuance, reregister to refresh the agent key for the insights service. Then run Register-AzureADConnectHealthAD FSAgent.
  8. Otherwise, you can run the insights service in console mode to catch errors. Go to C:\Program Files\Azure Ad Connect Health ADFS Agent\Insights and run Microsoft.Identity.Health.ADFS.InsightsService.exe /console.
  9. Look at the debug log and find exception items.

Source: Microsoft Learn / Windows Server documentation by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.

资料来源与适用范围

资料来源
Microsoft Learn / Windows Server documentation
适用范围
Windows Server · Source date 10/14/2024
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。