fix(intune-devices-manageddevice-list.md): Match output example to re…#9886
Open
promasu wants to merge 1 commit intomicrosoftgraph:mainfrom
Open
fix(intune-devices-manageddevice-list.md): Match output example to re…#9886promasu wants to merge 1 commit intomicrosoftgraph:mainfrom
promasu wants to merge 1 commit intomicrosoftgraph:mainfrom
Conversation
Contributor
|
Learn Build status updates of commit 1e5454d: ✅ Validation status: passed
For more details, please refer to the build report. |
Author
|
@microsoft-github-policy-service agree |
Contributor
|
@jaiprakashmb, this PR was created by an external contributor. Would you mind taking a look at it. Thanks! |
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the List managedDevices API reference topic to better reflect observed differences in example responses returned by the collection (/managedDevices) endpoint compared to the single-entity (/managedDevices/{id}) endpoint.
Changes:
- Adjusts the example response payload for
GET /deviceManagement/managedDevices(for example, empty arrays,nullvalues, and simplified timestamps). - Adds inline annotations in the example response to call out endpoint-specific behaviors.
- Updates the front matter
ms.date.
Comment on lines
74
to
+78
| "deviceName": "Device Name value", | ||
| "managedDeviceOwnerType": "company", | ||
| "deviceActionResults": [ | ||
| { | ||
| "@odata.type": "microsoft.graph.deviceActionResult", | ||
| "actionName": "Action Name value", | ||
| "actionState": "pending", | ||
| "startDateTime": "2016-12-31T23:58:46.7156189-08:00", | ||
| "lastUpdatedDateTime": "2017-01-01T00:00:56.8321556-08:00" | ||
| } | ||
| ], | ||
| "deviceActionResults": [], # Value always empty | ||
| "managementState": "retirePending", | ||
| "enrolledDateTime": "2016-12-31T23:59:43.797191-08:00", | ||
| "lastSyncDateTime": "2017-01-01T00:02:49.3205976-08:00", | ||
| "enrolledDateTime": "2016-12-31T23:59:43-08:00", |
| "remoteAssistanceSessionUrl": "https://example.com/remoteAssistanceSessionUrl/", | ||
| "remoteAssistanceSessionErrorDetails": "Remote Assistance Session Error Details value", | ||
| "remoteAssistanceSessionUrl": null, # Returns null when not set | ||
| "remoteAssistanceSessionErrorDetails": "Remote Assistance Session Error Details value", # Returns null when not set |
| ms.subservice: "intune" | ||
| doc_type: apiPageType | ||
| ms.date: 08/01/2024 | ||
| ms.date: 05/05/2026 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
…ality
Important
Required for API changes:
Add other supporting information, such as a description of the PR changes:
The outputs from the
https://graph.microsoft.com/v1.0/deviceManagement/managedDevicesandhttps://graph.microsoft.com/v1.0/deviceManagement/managedDevices/{managedDeviceId}deviate strongly but the differences are not shown in the example outputs, they even suggest that the outputs are the same.This change brings clarity within the documentation, when adhering to REST principals and providing consistent outputs across different endpoints regarding the same entity seems not wanted.
Important
The following guidance is for Microsoft employees only. Community contributors can ignore this message; our content team will manage the status.
After you've created your PR, expand this section for tips and additional instructions.
#feedback-addressedto the pull request.For more information, see the Content review process summary.