Home
%3CLINGO-SUB%20id%3D%22lingo-sub-438996%22%20slang%3D%22en-US%22%3EPublic%20endpoint%20for%20SQL%20Database%20Managed%20Instance%20is%20available%20as%20of%20today%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-438996%22%20slang%3D%22en-US%22%3E%3CDIV%3E(originally%20published%20on%26nbsp%3B%3CSPAN%3E%E2%80%8EApril%2011%2C%202019)%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%3EPublic%20endpoint%20for%20Azure%20SQL%20Database%20Managed%20Instance%20provides%20the%20ability%20to%20connect%20to%20Azure%20SQL%20Database%20Managed%20Instance%20from%20the%20Internet%20without%20using%20a%20VPN%20and%20is%20for%20data%20communication%20only.%20Public%20endpoint%20for%20data%20can%20simultaneously%20coexist%20with%20the%20private%20endpoint.%20With%20global%20availability%20as%20of%20today%2C%20this%20feature%20will%20help%20support%20many%20new%20integration%20scenarios.%26nbsp%3B%3CSPAN%3EFor%20security%20reasons%2C%20the%20implementation%20allows%20for%20Separation%20of%20Duties%20(SoD)%20between%20a%20database%20administrator%20and%20a%20network%20administrator%20when%20enabling%20the%20public%20endpoint.%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%3EThe%20public%20endpoint%20for%20managed%20instance%20can%20today%20be%20enabled%2Fdisabled%20via%20PowerShell%20script.%20%3CSTRIKE%3EThe%20support%20for%20Azure%20portal%20will%20be%20coming%20within%20the%20next%20two%20weeks%20or%20so%2C%20as%20soon%20as%20all%20updates%20are%20rolled%20out.%3C%2FSTRIKE%3E%26nbsp%3B%3CSPAN%20style%3D%22font-family%3A%20inherit%3B%22%3EUpdate%20(May%207%2C%202019)%3A%20%3C%2FSPAN%3E%3CSPAN%20style%3D%22font-family%3A%20inherit%3B%22%3EConfiguration%20of%20public%20endpoint%20for%20Managed%20Instance%20is%20now%20also%20available%20via%20Azure%20portal%3C%2FSPAN%3E%3CSPAN%20style%3D%22font-family%3A%20inherit%3B%22%3E%2C%20see%26nbsp%3B%3C%2FSPAN%3E%3CA%20style%3D%22font-family%3A%20inherit%3B%20background-color%3A%20%23ffffff%3B%22%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fazure%2Fsql-database%2Fsql-database-managed-instance-public-endpoint-configure%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EConfigure%20public%20endpoint%20in%20Azure%20SQL%20Database%20managed%20instance%3C%2FA%3E%3CSPAN%20style%3D%22font-family%3A%20inherit%3B%22%3E.%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%3E%0A%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%0A%3C%2FDIV%3E%0A%3CDIV%3E%3CSTRONG%3ESecurity%20requirements%20and%20separation%20of%20duties%3C%2FSTRONG%3E%3C%2FDIV%3E%0A%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%3ETo%20enable%20public%20endpoint%20for%20managed%20instance%2C%20two%20steps%20are%20required%2C%20and%20for%20separation%20of%20duties%20two%20separate%20roles%20with%20the%20following%20database%20and%20network%20permissions%20need%20to%20perform%20these%20steps%3A%3C%2FDIV%3E%0A%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CUL%3E%0A%3CLI%3EDatabase%26nbsp%3B%3CSPAN%3Eadministrator%3C%2FSPAN%3E%20who%20has%26nbsp%3BRBAC%20permissions%20in%20scope%20Microsoft.Sql%2FmanagedInstances%2F*%20needs%20to%20run%20a%20PowerShell%20script%20to%20enable%20public%20endpoint%20for%20managed%20instance.%20However%2C%20the%20public%20endpoint%20will%20not%20be%20accessible%20from%20the%20Internet%20until%20the%20second%20step%20by%20network%26nbsp%3B%3CSPAN%3Eadministrator%3C%2FSPAN%3E%20is%20performed.%3C%2FLI%3E%0A%3CLI%3ENetwork%26nbsp%3B%3CSPAN%3Eadministrator%3C%2FSPAN%3E%20who%20has%20RBAC%20permissions%20in%20scope%20Microsoft.Network%2F%20*%20needs%20to%20open%20the%20port%203342%20used%20by%20the%20public%20endpoint%20on%20NSG%20and%20provide%26nbsp%3BUDR%20route%20to%20avoid%20asymmetric%20routing.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%3E%3CSTRONG%3EEnable%20public%20endpoint%20for%20data%3C%2FSTRONG%3E%3C%2FDIV%3E%0A%3CDIV%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3ETo%20enable%20public%20endpoint%20for%20data%2C%20please%20follow%20these%20steps%3A%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E1.%20Database%20administrator%20with%20appropriate%20permissions%20needs%20to%20execute%20the%20below%20provided%20Power%20Shell%26nbsp%3Bscript.%26nbsp%3BPlease%20replace%20%7Bsubscription-id%7D%20with%20your%20subscription%2C%20replace%20%7Brg-name%7D%20with%20the%20resource%20group%20to%20which%20managed%20instance%20was%20deployed%2C%20and%20replace%20%7Bmi-name%7D%20with%20the%20name%20of%20your%20managed%20instance.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%0A%3CDIV%3E%0A%3CTABLE%20class%3D%22%20cke_show_border%22%20title%3D%22%22%20summary%3D%22%22%3E%0A%3CTBODY%3E%0A%3CTR%3E%0A%3CTD%3E%3CDIV%3EInstall-Module%20-Name%20Az%3C%2FDIV%3E%0A%3CDIV%3EImport-Module%20Az.Accounts%3C%2FDIV%3E%0A%3CDIV%3EImport-Module%20Az.Sql%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%3EConnect-AzAccount%3C%2FDIV%3E%0A%3CDIV%3ESelect-AzSubscription%20-SubscriptionId%20%7Bsubscription-id%7D%3C%2FDIV%3E%0A%3CDIV%3E%24mi%20%3D%20Get-AzSqlInstance%20-ResourceGroupName%20%7Brg-name%7D%20-Name%20%7Bmi-name%7D%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%3E%24mi%20%3D%20%24mi%20%7C%20Set-AzSqlInstance%20-PublicDataEndpointEnabled%20%24true%20-force%3C%2FDIV%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3C%2FTBODY%3E%0A%3C%2FTABLE%3E%0A%3C%2FDIV%3E%0A%3CP%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E2.%20Network%20administrator%20with%20appropriate%20permissions%20needs%20to%20setup%20an%20NSG%20to%20open%20the%20port%203342%20for%20the%20inbound%20traffic.%20You%20can%20follow%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fazure%2Fsql-database%2Fsql-database-managed-instance-public-endpoint-configure%23allow-public-endpoint-traffic-on-the-network-security-group%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ethis%20guide%3C%2FA%3E.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EPlease%20note%20the%20port%203342%20is%20used%20for%20public%20endpoint%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fopenspecs%2Fwindows_protocols%2Fms-tds%2F893fcc7e-8a39-4b3c-815a-773b7b982c50%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3ETDS%20connections%3C%2FA%3E%20to%20managed%20instance.%26nbsp%3BThis%20port%20cannot%20be%20customized.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EThe%20above%20steps%20complete%20the%20process%20of%20enabling%20public%20endpoint%20for%20managed%20instance.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EUse%20public%20endpoint%20from%20%3C%2FSTRONG%3E%3CSTRONG%3Eclients%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3ETo%20access%20managed%20instance%20from%20clients%20through%20the%20Internet%2C%20your%20application(s)%20need%20to%20use%20the%20hostname%20of%20the%20following%20format%20(the%20%22.public%22%20is%20added%20after%20the%20managed%20instance%20name%2C%20including%20the%20port)%3A%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E.%3CSTRONG%3Epublic%3C%2FSTRONG%3E.%3CDNS-ZONE%3E.database.windows.net%2C%3CSTRONG%3E3342%3C%2FSTRONG%3E%3C%2FDNS-ZONE%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3ESee%20the%20example%20of%20connecting%20with%20SSMS%20through%20the%20public%20endpoint%20to%20managed%20instance%20in%20the%20image%20below.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20805px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F108399iFAE062A375972D07%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22D38K-2rU0AYUR0m.png%22%20title%3D%22D38K-2rU0AYUR0m.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EDisable%20public%20endpoint%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EIn%20case%20you%20need%20to%20disable%20the%20public%20endpoint%2C%20database%20administrator%20needs%20to%20execute%26nbsp%3Bthe%20following%20Power%20Shell%26nbsp%3Bcommand%3A%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%0A%3CDIV%3E%0A%3CTABLE%20class%3D%22%20cke_show_border%22%20title%3D%22%22%20summary%3D%22%22%3E%0A%3CTBODY%3E%0A%3CTR%3E%0A%3CTD%3E%3CDIV%3ESet-AzSqlInstance%20-PublicDataEndpointEnabled%20%24false%20-force%3C%2FDIV%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3C%2FTBODY%3E%0A%3C%2FTABLE%3E%0A%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%3E%0A%3CP%3E%3CSPAN%3EIn%20addition%2C%20network%20administrator%20needs%20to%20remove%20the%20NSG%20rule%20for%20the%20inbound%20port%203342.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3C%2FDIV%3E%0A%3CDIV%3E%3CSTRONG%3EProduct%20road%20map%3C%2FSTRONG%3E%3C%2FDIV%3E%0A%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%3E%0A%3CP%3E%3CSPAN%3EWithin%20the%20next%20period%20as%20soon%20as%20all%20updates%20are%20rolled%20out%2C%20it%20will%20also%20be%20possible%20to%20enable%2Fdisable%20public%20endpoint%20from%20the%20Azure%20portal%20(within%20Managed%20Instance%20resource%2C%20Virtual%20network).%20In%20addition%2C%20the%20option%20to%20enable%2Fdisable%20public%20endpoint%20will%20also%20show%20at%20the%20time%20of%20creating%20a%20new%20Managed%20Instance.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%3EPublic%20endpoint%20feature%20for%20managed%20instance%20is%20now%20a%20production%20ready%20service.%26nbsp%3B%3CSTRIKE%3EDocumentation%20and%20further%20announcements%20will%20follow.%3C%2FSTRIKE%3E%26nbsp%3BUpdate%20(May%207%2C%202019)%3A%20Public%20documentation%20is%20now%20available%2C%20see%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fazure%2Fsql-database%2Fsql-database-managed-instance-public-endpoint-configure%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EConfigure%20public%20endpoint%20in%20Azure%20SQL%20Database%20managed%20instance%3C%2FA%3E.%3C%2FDIV%3E%0A%3CDIV%3E%3CBR%20%2F%3EAzure%20SQL%20Database%20Managed%20Instance%20Product%20Group%3C%2FDIV%3E%0A%3C%2FDIV%3E%0A%3C%2FDIV%3E%0A%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-438996%22%20slang%3D%22en-US%22%3E%3CP%3EPublic%20endpoint%20for%20Azure%20SQL%20Database%20Managed%20Instance%20provides%20the%20ability%20to%20connect%20to%20Azure%20SQL%20Database%20Managed%20Instance%20from%20the%20Internet%20without%20using%20a%20VPN%20and%20is%20for%20data%20communication%20only.%20Public%20endpoint%20for%20data%20can%20simultaneously%20coexist%20with%20the%20private%20endpoint.%20With%20global%20availability%20as%20of%20today%2C%20this%20feature%20will%20help%20support%20many%20new%20integration%20scenarios.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-SUB%20id%3D%22lingo-sub-776169%22%20slang%3D%22en-US%22%3ERe%3A%20Public%20endpoint%20for%20SQL%20Database%20Managed%20Instance%20is%20available%20as%20of%20today%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-776169%22%20slang%3D%22en-US%22%3E%3CP%3EPlease%20mention%20%2C3342%20format%20so%20that%20user%20can%20understand%20and%20does%20not%20have%20to%20figure%20out%20with%20this%20blog%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-778946%22%20slang%3D%22en-US%22%3ERe%3A%20Public%20endpoint%20for%20SQL%20Database%20Managed%20Instance%20is%20available%20as%20of%20today%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-778946%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F185220%22%20target%3D%22_blank%22%3E%40Sumit%20Kute%3C%2FA%3E%26nbsp%3B%20Thank%20you%20on%20your%20feedback.%20Please%20let%20me%20know%20where%20exactly%20did%20you%20mean%20to%20mention%20%2C3342%3F%20As%20this%20is%20mentioned%20in%20this%20blog%20post%2C%20I%20presume%20you%20perhaps%20might%20be%20asking%20about%20it%20in%20the%20portal%2C%20or%20some%20other%20place%3F%20Can%20you%20please%20clarify.%20Thank%20you.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-781358%22%20slang%3D%22en-US%22%3ERe%3A%20Public%20endpoint%20for%20SQL%20Database%20Managed%20Instance%20is%20available%20as%20of%20today%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-781358%22%20slang%3D%22en-US%22%3E%3CP%3EYes.%20Sorry%20missed%20it%2C%20I%20mean%20in%20Azure%20Docs.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-781386%22%20slang%3D%22en-US%22%3ERe%3A%20Public%20endpoint%20for%20SQL%20Database%20Managed%20Instance%20is%20available%20as%20of%20today%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-781386%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F185220%22%20target%3D%22_blank%22%3E%40Sumit%20Kute%3C%2FA%3E.%26nbsp%3BThanks.%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fsql-database%2Fsql-database-managed-instance-public-endpoint-configure%23obtaining-the-managed-instance-public-endpoint-connection-string%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EPublic%20documentation%3C%2FA%3E%26nbsp%3Bin%20Azure%20docs%20does%20specify%20port%203342%20needs%20to%20be%20used%20for%20the%20connection.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Microsoft
(originally published on ‎April 11, 2019)
 
Public endpoint for Azure SQL Database Managed Instance provides the ability to connect to Azure SQL Database Managed Instance from the Internet without using a VPN and is for data communication only. Public endpoint for data can simultaneously coexist with the private endpoint. With global availability as of today, this feature will help support many new integration scenarios. For security reasons, the implementation allows for Separation of Duties (SoD) between a database administrator and a network administrator when enabling the public endpoint.
 
The public endpoint for managed instance can today be enabled/disabled via PowerShell script. The support for Azure portal will be coming within the next two weeks or so, as soon as all updates are rolled out. Update (May 7, 2019): Configuration of public endpoint for Managed Instance is now also available via Azure portal, see Configure public endpoint in Azure SQL Database managed instance.
 
Security requirements and separation of duties
 
To enable public endpoint for managed instance, two steps are required, and for separation of duties two separate roles with the following database and network permissions need to perform these steps:
 
  • Database administrator who has RBAC permissions in scope Microsoft.Sql/managedInstances/* needs to run a PowerShell script to enable public endpoint for managed instance. However, the public endpoint will not be accessible from the Internet until the second step by network administrator is performed.
  • Network administrator who has RBAC permissions in scope Microsoft.Network/ * needs to open the port 3342 used by the public endpoint on NSG and provide UDR route to avoid asymmetric routing.
 
Enable public endpoint for data

 

To enable public endpoint for data, please follow these steps:

 

1. Database administrator with appropriate permissions needs to execute the below provided Power Shell script. Please replace {subscription-id} with your subscription, replace {rg-name} with the resource group to which managed instance was deployed, and replace {mi-name} with the name of your managed instance.

 

Install-Module -Name Az
Import-Module Az.Accounts
Import-Module Az.Sql 
Connect-AzAccount
Select-AzSubscription -SubscriptionId {subscription-id}
$mi = Get-AzSqlInstance -ResourceGroupName {rg-name} -Name {mi-name} 
$mi = $mi | Set-AzSqlInstance -PublicDataEndpointEnabled $true -force

 

2. Network administrator with appropriate permissions needs to setup an NSG to open the port 3342 for the inbound traffic. You can follow this guide.

 

Please note the port 3342 is used for public endpoint TDS connections to managed instance. This port cannot be customized. 

 

The above steps complete the process of enabling public endpoint for managed instance.

 

Use public endpoint from clients

 

To access managed instance from clients through the Internet, your application(s) need to use the hostname of the following format (the ".public" is added after the managed instance name, including the port):

 

<mi-name>.public.<dns-zone>.database.windows.net,3342

 

See the example of connecting with SSMS through the public endpoint to managed instance in the image below.

 

D38K-2rU0AYUR0m.png

Disable public endpoint

 

In case you need to disable the public endpoint, database administrator needs to execute the following Power Shell command:

 

Set-AzSqlInstance -PublicDataEndpointEnabled $false -force
 

In addition, network administrator needs to remove the NSG rule for the inbound port 3342.

 

Product road map
 

Within the next period as soon as all updates are rolled out, it will also be possible to enable/disable public endpoint from the Azure portal (within Managed Instance resource, Virtual network). In addition, the option to enable/disable public endpoint will also show at the time of creating a new Managed Instance.

 
Public endpoint feature for managed instance is now a production ready service. Documentation and further announcements will follow. Update (May 7, 2019): Public documentation is now available, see Configure public endpoint in Azure SQL Database managed instance.

Azure SQL Database Managed Instance Product Group
4 Comments
Microsoft

Please mention ,3342 format so that user can understand and does not have to figure out with this blog

Microsoft

@Sumit Kute  Thank you on your feedback. Please let me know where exactly did you mean to mention ,3342? As this is mentioned in this blog post, I presume you perhaps might be asking about it in the portal, or some other place? Can you please clarify. Thank you.

Microsoft

Yes. Sorry missed it, I mean in Azure Docs.

Microsoft

@Sumit Kute. Thanks. Public documentation in Azure docs does specify port 3342 needs to be used for the connection.