microsoftgraph / microsoftgraph/msgraph-beta-sdk-dotnet

Potential incorrect deprecation notice for RoleManagementRequestBuilder.Directory in Graph SDK

Open
#1,074 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

status:waiting-for-triage type:bug
Dominant language
C#
Stars
112
Forks
37
Avg merge
14h 57m
Merged PRs (30d)
3

Description

Describe the bug

Hi team,

I’m encountering a deprecation warning in the Microsoft Graph .NET SDK related to the following API:

'RoleManagementRequestBuilder.Directory' is obsolete:
'This version is being deprecated and is scheduled for removal on 2025-12-01.
 Please migrate to the latest version before the removal date.
 as of 2025-01/PrivatePreview:microsoft.applicationAuthorization on 2025-01-01
 and will be removed 2025-12-01'

However, when making the corresponding Graph call, everything still works as expected, and I cannot find any documentation, changelog entry, roadmap note, or API announcement that indicates this endpoint will actually be deprecated.

Expected behavior

If the endpoint is truly being deprecated:

  • Documentation should reflect the planned removal date.
  • Migration guidance should be provided.

If not:

  • The Obsolete attribute in the SDK may need correction or clarification.
How to reproduce

Using the Graph .NET SDK (latest version as of the time of writing):

var result = await graphClient
    .RoleManagement
    .Directory
    .RoleAssignments
    .GetAsync();
SDK Version

5.126.0-preview

Latest version known to work for scenario above?

No response

Known Workarounds

No response

Debug output
Click to expand log ```
</details>


### Configuration

_No response_

### Other information

Could you confirm whether:

- [ ] This endpoint is actually deprecated, and documentation is missing.
- [ ] The deprecation attribute was applied incorrectly in the SDK?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the RoleManagementRequestBuilder.Directory call shown in the issue and inspect the Microsoft Graph .NET SDK 5.126.0-preview metadata for its Obsolete attribute. Compare the warning with the Graph API documentation, changelog, and roadmap for this endpoint. Done means confirming whether deprecation is intended and identifying the documentation or SDK metadata that requires correction.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
api
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.