[Hubs] Document how to move from private to public access and remove costly resources#1787
Merged
Conversation
Co-authored-by: MSBrett <24294904+MSBrett@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] [Hubs] Document how to move from private to public access
[Hubs] Document how to move from private to public access
Aug 1, 2025
MSBrett
reviewed
Aug 1, 2025
…letion order, enhance security recommendations Co-authored-by: MSBrett <24294904+MSBrett@users.noreply.github.com>
MSBrett
requested changes
Aug 1, 2025
MSBrett
left a comment
Contributor
There was a problem hiding this comment.
We need to put our changes into the unreleased section. V12 has already shipped.
Contributor
Author
The changelog entry is already in the "Unreleased" section (line 30). It was moved there in commit 61c9619 to address the earlier review feedback. |
MSBrett
requested changes
Aug 1, 2025
MSBrett
left a comment
Contributor
There was a problem hiding this comment.
Add a section which details removing the managed runtime from Azure Data Factory along with the managed private endpoints. Whilst leaving them won't break anything they do carry a cost, so it's best to remove them.
Co-authored-by: MSBrett <24294904+MSBrett@users.noreply.github.com>
Contributor
Author
Added a new section detailing how to remove the Azure Data Factory managed integration runtime along with managed private endpoints. The section includes step-by-step instructions for identifying, stopping, and deleting managed integration runtimes to eliminate ongoing costs. Commit e92bb86 |
Copilot
AI
changed the title
[Hubs] Document how to move from private to public access
[Hubs] Document how to move from private to public access and remove costly resources
Aug 1, 2025
MSBrett
requested changes
Aug 4, 2025
…access Co-authored-by: MSBrett <24294904+MSBrett@users.noreply.github.com>
MSBrett
approved these changes
Aug 4, 2025
arthurclares
approved these changes
Aug 6, 2025
flanakin
pushed a commit
that referenced
this pull request
Jan 31, 2026
…costly resources (#1787) Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: MSBrett <24294904+MSBrett@users.noreply.github.com>
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.
This PR adds comprehensive documentation to help customers reduce costs by switching their FinOps hubs from private to public networking access, including removal of all cost-generating resources.
Background
Private networking in FinOps hubs adds significant costs for virtual networks, private endpoints, dedicated compute resources, and managed integration runtimes. Many customers who initially deployed with private access may later want to reduce costs by switching to public access, which is still secure through RBAC and TLS encryption.
Changes Made
Added new section "Removing private networking" to
docs-mslearn/toolkit/hubs/private-networking.md:Updated changelog in
docs-mslearn/toolkit/changelog.md:The documentation provides clear guidance on how to make this transition safely, including important considerations about planning the change, coordinating with network administrators, verifying the deployment works correctly after the switch, and properly cleaning up all networking resources and managed runtimes in the correct order to avoid dependency conflicts and eliminate all associated costs.
Fixes #1342.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.