Microsoft graph api 如何使用Microsoft Graph检索通讯组列表的所有者?
我不确定是否发现了bug,或者是否使用了错误的方法:我无法使用Graph检索DL组的所有者 步骤:Microsoft graph api 如何使用Microsoft Graph检索通讯组列表的所有者?,microsoft-graph-api,Microsoft Graph Api,我不确定是否发现了bug,或者是否使用了错误的方法:我无法使用Graph检索DL组的所有者 步骤: 假设我的电子邮件是admin@contoso.com. 我在Exchange服务器的Microsoft 365管理中心中创建了一个通讯组列表组,并将自己(管理员)设置为该DL的所有者。我把这个DL命名为“TestDG1”。我还添加了这个用户作为DL的唯一成员 然后,我访问了,以管理员身份登录,授予自己访问组、联系人、用户的读取权限,并执行此查询: 我通过以下信息获得了成功的回复: { "
{
"@odata.context": "https://graph.microsoft.com/v1.0/$metadata#groups",
"value": [
{
"id": "01234567-89AB-CDEF-0123-456789ABCDEF",
"deletedDateTime": null,
"classification": null,
"createdDateTime": "2018-10-15T18:38:08Z",
"creationOptions": [],
"description": null,
"displayName": "TestDG1",
"groupTypes": [],
"mail": "testdg1@contoso.com",
"mailEnabled": true,
"mailNickname": "TestDG1",
"onPremisesLastSyncDateTime": null,
"onPremisesSecurityIdentifier": null,
"onPremisesSyncEnabled": null,
"preferredDataLocation": null,
"proxyAddresses": [
"SMTP:testdg1@contoso.com"
],
"renewedDateTime": "2018-10-15T18:38:08Z",
"resourceBehaviorOptions": [],
"resourceProvisioningOptions": [],
"securityEnabled": false,
"visibility": null,
"onPremisesProvisioningErrors": []
}
]
}
{
"@odata.context": "https://graph.microsoft.com/v1.0/$metadata#groups/$entity",
"id": "01234567-89AB-CDEF-0123-456789ABCDEF",
"deletedDateTime": null,
"classification": null,
"createdDateTime": "2018-10-15T18:38:08Z",
"creationOptions": [],
"description": null,
"displayName": "TestDG1",
"groupTypes": [],
"mail": "testdg1@contoso.com",
"mailEnabled": true,
"mailNickname": "TestDG1",
"onPremisesLastSyncDateTime": null,
"onPremisesSecurityIdentifier": null,
"onPremisesSyncEnabled": null,
"preferredDataLocation": null,
"proxyAddresses": [
"SMTP:testdg1@contoso.com"
],
"renewedDateTime": "2018-10-15T18:38:08Z",
"resourceBehaviorOptions": [],
"resourceProvisioningOptions": [],
"securityEnabled": false,
"visibility": null,
"onPremisesProvisioningErrors": []
}
{
"@odata.context": "https://graph.microsoft.com/v1.0/$metadata#groups",
"value": [
{
"id": "01234567-89AB-CDEF-0123-456789ABCDEF",
"deletedDateTime": null,
"classification": null,
"createdDateTime": "2018-10-15T18:38:08Z",
"creationOptions": [],
"description": null,
"displayName": "TestDG1",
"groupTypes": [],
"mail": "testdg1@contoso.com",
"mailEnabled": true,
"mailNickname": "TestDG1",
"onPremisesLastSyncDateTime": null,
"onPremisesSecurityIdentifier": null,
"onPremisesSyncEnabled": null,
"preferredDataLocation": null,
"proxyAddresses": [
"SMTP:testdg1@contoso.com"
],
"renewedDateTime": "2018-10-15T18:38:08Z",
"resourceBehaviorOptions": [],
"resourceProvisioningOptions": [],
"securityEnabled": false,
"visibility": null,
"onPremisesProvisioningErrors": [],
"owners": []
}
]
}
{
"@odata.context": "https://graph.microsoft.com/v1.0/$metadata#directoryObjects",
"value": []
}
B) 直接查询DL的所有者:
我获得了成功的响应,但值数组为空:
{
"@odata.context": "https://graph.microsoft.com/v1.0/$metadata#groups",
"value": [
{
"id": "01234567-89AB-CDEF-0123-456789ABCDEF",
"deletedDateTime": null,
"classification": null,
"createdDateTime": "2018-10-15T18:38:08Z",
"creationOptions": [],
"description": null,
"displayName": "TestDG1",
"groupTypes": [],
"mail": "testdg1@contoso.com",
"mailEnabled": true,
"mailNickname": "TestDG1",
"onPremisesLastSyncDateTime": null,
"onPremisesSecurityIdentifier": null,
"onPremisesSyncEnabled": null,
"preferredDataLocation": null,
"proxyAddresses": [
"SMTP:testdg1@contoso.com"
],
"renewedDateTime": "2018-10-15T18:38:08Z",
"resourceBehaviorOptions": [],
"resourceProvisioningOptions": [],
"securityEnabled": false,
"visibility": null,
"onPremisesProvisioningErrors": [],
"owners": []
}
]
}
{
"@odata.context": "https://graph.microsoft.com/v1.0/$metadata#directoryObjects",
"value": []
}
这是一个错误,还是我做错了什么?如果是一个bug,我应该在哪里报告它?目前(2019-04-18),启用邮件的安全组和通讯组列表的所有者当前不包括在Microsoft Graph中的
所有者中。所有者当前仅可用于安全组(未启用邮件)和Office 365组。我也可以复制此信息。所以应该是臭虫。对于bug,您可以在Github问题列表中报告它,并将其标记为bug。对于无bug开发问题,请将其发布在StackOverFlow上。对于功能请求,请在UserVoice上发布它们。好的,谢谢。我在这里报告了这个问题:SeiyaSu,我是否在正确的位置记录了这个bug?这件事多久会被发现?让我看看是否能找到一位知道这个问题答案的首相。这是归档这些服务错误的正确位置。GitHub是SDK bug的一个选项,但由于这是一个服务问题,这里是正确的位置。