Skip to content

Update Intune endpoints with new Azure Front Door IPs - #5231

Open
RFC2784 wants to merge 1 commit into
MicrosoftDocs:mainfrom
RFC2784:patch-1
Open

Update Intune endpoints with new Azure Front Door IPs#5231
RFC2784 wants to merge 1 commit into
MicrosoftDocs:mainfrom
RFC2784:patch-1

Conversation

@RFC2784

@RFC2784 RFC2784 commented Aug 25, 2026

Copy link
Copy Markdown

Added new Azure Front Door IP ranges for Intune endpoints.

Added new Azure Front Door IP ranges for Intune endpoints.
@prmerger-automator

Copy link
Copy Markdown
Contributor

RFC2784 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. Paolo Matarazzo (@paolomatarazzo)

@prmerger-automator

Copy link
Copy Markdown
Contributor

RFC2784 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. Paolo Matarazzo (@paolomatarazzo)

@learn-build-service-prod

Copy link
Copy Markdown
Contributor

Learn Build status updates of commit e96ea7d:

✅ Validation status: passed

File Status Preview URL Details
intune/fundamentals/endpoints.md ✅Succeeded

For more details, please refer to the build report.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the Intune endpoint documentation to include newly added Azure Front Door IP ranges, keeping the published endpoint lists aligned with the latest service tag data.

Changes:

  • Added 150.171.109.0/24 and 150.171.110.0/24 to the “Azure Front Door Endpoints” list for the Intune client/host service entry.
  • Added the same IP ranges to the “IP Subnets” section for completeness/consistency.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

13.107.228.0/23
150.171.97.0/24
150.171.109.0/24
150.171.110.0/24
@v-dirichards

Copy link
Copy Markdown
Contributor

Albert Cabello Serrano (@iceorbital)

Can you review the proposed changes?

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator Bot added the aq-pr-triaged Tracking label for the PR review team label Aug 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants