Update intune-shared-deviceappmanagement-get.md

[andyrobbins]

Correct formatting of "Permissions" section header by removing leading whitespace.

Important

Required for API changes:

• Link to API.md file: ADD LINK HERE
• Link to PR for public-facing schema changes (schema-Prod-beta/v1.0.csdl): ADD LINK HERE

---

Add other supporting information, such as a description of the PR changes:

The Microsoft Learn page that renders this markdown is formatting the "Permissions" section header as a code block due to the leading whitespace. This PR fixes this by removing the leading whitespace.

---

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.

• do not merge is the default PR status and is automatically added to all open PRs that don't have the ready to merge label.
• Add the ready for content review label to start a review. Only PRs that have met the minimum requirements for content review and have this label are reviewed.
• If your content reviewer requests changes, review the feedback and address accordingly as soon as possible to keep your pull request moving forward. After you address the feedback, remove the changes requested label, add the review feedback addressed label, and select the Re-request review icon next to the content reviewer's alias. If you can't add labels, add a comment with #feedback-addressed to the pull request.
• After the content review is complete, your reviewer will add the content review complete label. When the updates in this PR are ready for external customers to use, replace the do not merge label with ready to merge and the PR will be merged within 24 working hours.
• Pull requests that are inactive for more than 6 weeks will be automatically closed. Before that, you receive reminders at 2 weeks, 4 weeks, and 6 weeks. If you still need the PR, you can reopen or recreate the request.

For more information, see the Content review process summary.

[learn-build-service-prod]

Learn Build status updates of commit 53fa6bf:

⚠️ Validation status: warnings

File	Status	Preview URL	Details
api-reference/beta/api/intune-shared-deviceappmanagement-get.md	⚠️Warning		Details

api-reference/beta/api/intune-shared-deviceappmanagement-get.md

• Line 2, Column 8: [Warning: duplicate-titles - See documentation] Title 'Get deviceAppManagement - Microsoft Graph beta' is duplicated in: 'beta/api/intune-devices-deviceappmanagement-get.md(2,8), beta/api/intune-shared-deviceappmanagement-get.md(2,8)'. Titles must be unique within a docset.
• Line 11, Column 1: [Warning: duplicate-h1s - See documentation] H1 'Get deviceAppManagement' is duplicated with other articles: 'beta/api/intune-devices-deviceappmanagement-get.md(11,1), beta/api/intune-shared-deviceappmanagement-get.md(11,1)'. First level headings must be unique within a docset.
• Line 3, Column 14: [Suggestion: duplicate-descriptions - See documentation] Attribute 'description' with value 'Read properties and relationships of the deviceAppManagement object.' is duplicated in 'beta/api/intune-devices-deviceappmanagement-get.md(3,14)', 'beta/api/intune-shared-deviceappmanagement-get.md(3,14)'.
• Line 6, Column 1: [Suggestion: ms-prod-disallowed - See documentation] ms.prod is deprecated and can't be used for all content.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[microsoft-github-policy-service]

Thank you for your work in this PR, @andyrobbins.

When the updates in this PR are ready for external customers to use, please replace the do not merge label with ready to merge.

Check the content review workflow here.