Fix broken changelog URLs in Microsoft.Intune.json (Intune Sprint 2607 PE Beta)

[Copilot]

The "Changelog link validation" CI job was failing on PR #9993 due to 21 broken URLs in newly added changelog/Microsoft.Intune.json entries.

Root cause: New entries used malformed URLs with two issues:

• /en-us/ locale prefix (link checker doesn't follow redirects)
• camelCase resource slugs without namespace prefix (e.g., intune-iosDdmLobAppAssignmentSettings) instead of the correct lowercase+namespaced filename format (e.g., intune-apps-iosddmlobappassignmentsettings)

Changes:

• Incorporates all changelog additions from Sprint 2607 PE Beta
• 10 URLs corrected to proper https://learn.microsoft.com/graph/api/resources/{namespace}-{lowercase-name} format:
  • iosDdmLobAppAssignmentSettings → intune-apps-iosddmlobappassignmentsettings
  • mobileAppContentFile → intune-apps-mobileappcontentfile
  • deviceConfigurationUserStateSummary → intune-deviceconfig-deviceconfigurationuserstatesummary
  • managedDevice → intune-devices-manageddevice
  • securityBaselineCategoryStateSummary, securityBaselineDeviceState, securityBaselineStateSummary, securityBaselineTemplate → intune-deviceintent-*
  • androidManagedAppProtection, windowsManagedAppProtection → intune-mam-*
  • beginOnboarding → intune-remoteassistance-remoteassistancepartner-beginonboarding (API path, not resources)
• 6 broken links converted to bold text for resources with no existing doc pages: iosDdmVppAppAssignmentSettings, macOsDdmVppAppAssignmentSettings, deviceManagement, securityBaselineSettingState, securityBaselineState, createRemoteHelpSessionResponse

---

Important

Use the AI-powered workflow for Graph onboarding to author and self-review schema-related changes. See https://aka.ms/msgraphcdk for more information.

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

---

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 a73c679:

⚠️ Validation status: warnings

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.

[learn-build-service-prod]

Learn Build status updates of commit 9fac7b6:

✅ Validation status: passed

File	Status	Preview URL	Details
changelog/Microsoft.Intune.json	✅Succeeded

For more details, please refer to the build report.