microsoft / microsoft/sql-server-samples
Update the "prepareSubnet.ps1" script to match the latest SQL MI Networking Requirements
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 11.2k
- Forks
- 9.1k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 14
Description
The prepareSubnet.ps1 script has been used in many deployments to automate the complex networking configuration for SQL MI for about 1 year or more.
Recently it seems the SQL MI connectivity requirements have changed and some configuration has been deprecated:
https://docs.microsoft.com/en-us/azure/azure-sql/managed-instance/connectivity-architecture-overview
"[Deprecated] Network requirements without service-aided subnet configuration
Deploy SQL Managed Instance in a dedicated subnet inside the virtual network. The subnet must have these characteristics:"
Particularly, the legacy prepareSubnet.ps1 script removes service endpoints from the subnet, while it appears that recently SQL MI subnets allow service endpoint configuration.
Therefore, it appears the script needs to be updated to implement the latest connectivity requirements, in particular, not removing service endpoints configured on the subnet.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading prepareSubnet.ps1 and the linked Azure SQL Managed Instance connectivity architecture requirements. Trace where the script removes subnet service endpoints and compare that behavior with the current requirements. Done means the script no longer removes permitted service endpoints and matches the documented networking configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, powershell
- Domain
- cloud, networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100