Skip to content

Commit d3b83a7

Browse files
Merge pull request #27954 from zoran-rilak-msft/sqlmi-privatelink-remove-knownissues
Remove Known Issues
2 parents 8475317 + cf2a527 commit d3b83a7

1 file changed

Lines changed: 0 additions & 4 deletions

File tree

azure-sql/managed-instance/private-endpoint-overview.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -44,10 +44,6 @@ The benefits of using private endpoints over a VNet-local or public endpoint inc
4444
- Avoiding address overlap: peering multiple virtual networks requires careful IP space allocation and can pose a problem when address spaces overlap.
4545
- Conserving IP address real estate: a private endpoint only consumes one IP address from its subnet's address space.
4646

47-
## Known issues
48-
49-
- Azure portal still shows the word "Preview" next to Private endpoint connections item in SQL Managed Instance's sidebar. This is incorrect; private endpoint connections for SQL Managed Instance are now generally available. The word "Preview" will be removed in an upcoming update.
50-
5147
## Limitations
5248

5349
- Azure SQL Managed Instance requires the exact instance _hostname_ to appear in the connection string sent by the SQL client. Using the IP address of the private endpoint is not supported and will fail. To resolve this, configure your DNS server, or use a private DNS zone as described in [Set up domain name resolution for private endpoint](#set-up-domain-name-resolution-for-private-endpoint).

0 commit comments

Comments
 (0)