microsoftgraph / microsoftgraph/microsoft-graph-explorer-v4
Query "https://graph.microsoft.com/beta/deviceManagement/hardwarePasswordDetails" produces Error 500
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 260
- Forks
- 110
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
When trying to query "https://graph.microsoft.com/beta/deviceManagement/hardwarePasswordDetails" with correct permissions (worked a few weeks ago) or even as global administrator, I get Error 500:
"message": "{\r\n "_version": 3,\r\n "Message": "An internal server error has occurred - Operation ID (for customer support): 00000000-0000-0000-0000-000000000000 - Activity ID: - Url: https://proxy.amsub0502.manage.microsoft.com/DeviceConfiguration_2605/StatelessDeviceConfigurationFEService/deviceManagement/hardwarePasswordDetails?api-version=5026-05-10\",\r\n "CustomApiErrorPhrase": "",\r\n "RetryAfter": null,\r\n "ErrorSourceService": "",\r\n "HttpHeaders": "{}"\r\n}",
To Reproduce
Steps to reproduce the behavior:
- Go to https://developer.microsoft.com/en-us/graph/graph-explorer
- Log in
- Query: https://graph.microsoft.com/beta/deviceManagement/hardwarePasswordDetails
- Run Query
- See error
Expected behavior
Give me all saved information of all devices in my tenant and let me filter the response.
Desktop (please complete the following information):
- OS: Windows 24H2
- Browser: Microsoft Edge und Mozilla Firefox
- Version: 149.0.4022.69 (Edge) und 150.0.3 (Firefox)
Smartphone (please complete the following information):
- Device:
- OS: iOS 18.7
- Browser: Safari
- Version: 18.7
Additional context
Does not work with powershell script and an enterprise app either.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the request in Microsoft Graph Explorer at the reported hardwarePasswordDetails endpoint, then compare it with the PowerShell script and enterprise app context described in the issue. Done would require identifying whether the 500 response is reproducible and documenting a confirmed cause or a clear maintainer handoff to the Microsoft Graph service.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100