topic Re: ArcGIS Pro 3.5 Connection Issue to Azure SQL Managed Instance with Microsoft Entra Authentication in ArcGIS Pro Questions

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

AYUSHYADAV — Fri, 11 Jul 2025 14:08:57 GMT

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#ESRI_SECTION2_7EAD939DEDF949638DB10BBE0EEEA36A:~:text=Microsoft%20Entra%20ID%20options,ID%20authentication%20options%3A), 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

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

AyanPalit — Fri, 11 Jul 2025 14:25:32 GMT

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

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

AYUSHYADAV — Mon, 14 Jul 2025 05:57:21 GMT

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

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

AYUSHYADAV — Mon, 14 Jul 2025 13:17:37 GMT

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

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

christinazhang2025 — Tue, 16 Sep 2025 23:01:56 GMT

We have been battling the same error in the Azure SQL with MS Entra Authentication. Esri giving the same response on Characters but I am not convinced because same long email user added to SQL login directly (without being in AD) is working fine!!! Characters is not a constrain in this scenario! Only when the users being a member in AD group that added to SQL login wouldn't go through. Short email such as db@domain in AD group works, long email name database.test@ doesn't work. Both being members in an AD group. So I am thinking something in the AD group and ODBC driver cause issue in the MS authentication because using PYODBC script defining the ODBC driver works!

This is the script solution for tool development: use PYODBC script to connect to SQL, but users need to browse the list of layers in the drop-down of Database folder pane! script can't achieve that.

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

christinazhang2025 — Wed, 05 Nov 2025 00:36:27 GMT

We got the same genetic Esri support response of 31 character but I don't think that's the case. Don't think it's related to ArcGIS Pro version either. We can use the Database connection tool interface connection to SQL when users long full email is directly added to login in SQL (without AD group). After some testing, found the Database Connection tool reach the Master db first then bounce back the badlogin error. Users are mapped in other databases. python pdodbc works because it didn't speak to master, go straight to the database specified. So in the Instance string, try specified the database to avoid the tool hitting Master: Database=<your DB>