-
Notifications
You must be signed in to change notification settings - Fork 34
Open
Labels
status:waiting-for-triageAn issue that is yet to be reviewed or assignedAn issue that is yet to be reviewed or assignedtype:bugA broken experienceA broken experience
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?
Metadata
Metadata
Assignees
Labels
status:waiting-for-triageAn issue that is yet to be reviewed or assignedAn issue that is yet to be reviewed or assignedtype:bugA broken experienceA broken experience