Microsoft Graph API BETA - 报告返回 userPrincipalName 加密/散列 [英] Microsoft Graph API BETA - Reports returning userPrincipalName encrypted/hashed

问题描述

调用报告端点之一时，例如 https://graph.microsoft.com/beta/reports/getTeamsUserActivityUserDetail(period='D7')?$format=application/json

When calling one of reports endpoints, eg https://graph.microsoft.com/beta/reports/getTeamsUserActivityUserDetail(period='D7')?$format=application/json

对于我们的租户，返回的 userPrincipalName 看起来类似于 91AFD71ACEEFDD92B5B0A041F0E2FDA6，但我在测试租户中看到了预期的电子邮件.

The userPrincipalName returned looks something like 91AFD71ACEEFDD92B5B0A041F0E2FDA6 for our tenant but I see the expected email in our test tenant.

我没有在文档中看到有关所需额外权限或其他潜在安全设置的任何内容.调用报告时如何获取实际的 UPN?

I didnt see anything in the documentation on additional permissions required or other potential security settings. How do I get the actual UPN when calling the reports?

推荐答案

对于未来可能遇到这种情况的其他人:

For others that may run into this in the future:

Office 365 管理员必须禁用设置->报告下的显示匿名标识符"设置.

An Office 365 administrator must disable the setting "Display anonymous identifiers" under Settings->Reports.

请参阅 MS 支持文档

这篇关于Microsoft Graph API BETA - 报告返回 userPrincipalName 加密/散列的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！