Azure-sdk-for-net: [BUG] `Microsoft.Azure.Graph.RBAC.Models.DirectoryObject` is missing all expandable properties

Created on 11 Nov 2020  路  12Comments  路  Source: Azure/azure-sdk-for-net

Describe the bug

If you browse the OData API (https://graph.windows.net/tenantid/$metadata), you will see the DirectoryObject has the following properties:

  • objectType
  • objectId
  • deletionTimestamp

and the following navigation properties:

  • createdOnBehalfOf
  • createdObjects
  • manager
  • directReports
  • members
  • transitiveMembers
  • memberOf
  • transitiveMemberOf
  • owners
  • ownedObjects

The problem is that all the navigation properties are not present in the DirectoryObject model.

Expected behavior

The navigation properties should be there.

Actual behavior (include Exception or Stack Trace)

There is no way to get the navigation properties, so no stack trace.

To Reproduce

no reproduction possible.

Environment:

not relevant. Is broken everywhere

Client Graph Service Attention customer-reported needs-team-attention question

Most helpful comment

Thank you for your feedback. Tagging and routing to the team best able to assist.

All 12 comments

Thank you for your feedback. Tagging and routing to the team best able to assist.

fyi

This is also more or less related to this issue: https://github.com/MicrosoftDocs/feedback/issues/1339

I wan't to solve this issue and needs the owners of the AdApplication. But I can't get it from the data model.

any updates on this @jsquire .

It would also help if anybody can provide the implementation of the function Start-AutoRestCodeGeneration. Then I can fix the bug by myself. But I can't find it.

The function is used here

Unfortunately, I'm only serving as first-line triage in this case. I don't have insight into the process that is used by the team that owns this library. Generally, there's a 72 hour window provided for teams to triage and respond. If we don't see engagement by the owners after 72 hours, please feel free to ping me again and I'll do what I'm able to escalate.

ping @jsquire ;) 72h are over 馃晲

Thank you for the ping, @paule96. I've started an internal thread to track down the correct owner and escalate.

Ping again @jsquire.
It would be good to have an update on this.

Hi @paule96. I apologize for the lack of engagement; we're still working internally to find the appropriate owner and get you some assistance. Unfortunately, while we're closer, I don't have a solid timeline. With the US holidays at the end of this week, we may be delayed until folks return to the office next week.

@jsquire

all good :) I just try to not forget this. So don't worry if I asking ever 72h. It's also a reminder for me. ^^

So any updates here?

No updates; the email thread was kicked but, as mentioned, the US holiday last week had many folks out. I'll kick it next on Wednesday, to give some time for those returning to get through their email backlog.

Just a quick note, there is still discussion ongoing internally. One key contact was out through last week. We apologize for the delay and confusion surrounding ownership here.

Thanks for letting me know. 馃憤 You do a great job!

Was this page helpful?
0 / 5 - 0 ratings