本文介绍了Microsoft Graph API BETA-报告返回的已加密/已哈希的userPrincipalName的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

在调用报告端点之一时,例如 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的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

10-31 01:39