Select to view content in your preferred language

ArcGIS Pro 3.5 Connection Issue to Azure SQL Managed Instance with Microsoft Entra Authentication

316
3
Jump to solution
07-11-2025 07:08 AM
AYUSHYADAV
Regular Contributor

Hi,

We are experiencing an issue connecting ArcGIS Pro 3.5 to an Azure SQL Server Managed Instance using Microsoft Entra authentication.

Environment:

  • Database: SQL Server Managed Instance on Azure Cloud

  • Client Application: ArcGIS Pro 3.5

  • Workstation: Both SSMS and ArcGIS Pro are installed on the same machine.

Problem Description:

As per the ArcGIS Pro documentation on database connections (specifically, the section on Microsoft Entra ID authentication options: https://pro.arcgis.com/en/pro-app/latest/help/data/databases/database-connections-in-arcgis-pro.htm#...), we should be able to leverage Microsoft Entra authentication for this connection.

We are successfully able to connect to the SQL Server Managed Instance database via SQL Server Management Studio (SSMS) using the Microsoft Entra authentication options (e.g., Azure Active Directory - Universal with MFA, Azure Active Directory - Password).

Furthermore, we are able to successfully connect to the SQL Server database using database authentication (SQL Server Authentication) via ArcGIS Pro.

However, when attempting to connect to the same instance from ArcGIS Pro v3.5 using the same Microsoft Entra authentication method and credentials, we consistently receive the error: "Bad user login."

We have meticulously verified the username and password multiple times to ensure their correctness.

Any help from anyone will be highly appreciated. 

Thank you,

Ayush

Tags (2)
0 Kudos
1 Solution

Accepted Solutions
AYUSHYADAV
Regular Contributor

ESRI Support has confirmed that this is a bug affecting usernames longer than 31 characters. Here is the enhancement number. - ENH-000121539

View solution in original post

0 Kudos
3 Replies
AyanPalit
Esri Regular Contributor

@AYUSHYADAV Was the successful connection with different version of Pro?  So it worked before and the only known change is ArcGIS Pro v3.5?

Ayan Palit | Principal Consultant Esri
0 Kudos
AYUSHYADAV
Regular Contributor

Hi @AyanPalit , 

I have tested this with versions 3.3, 3.4 & 3.5. It is giving me the same error, "Bad user login," for all three versions.

Thanks

Ayush

0 Kudos
AYUSHYADAV
Regular Contributor

ESRI Support has confirmed that this is a bug affecting usernames longer than 31 characters. Here is the enhancement number. - ENH-000121539

0 Kudos