cannot connect to azure analysis services from ssms

TammyReaume-5087 0 Reputation points

Microsoft Entra Id is both owner in AIM roles and is in the Analysis service admins. I am trying to connect so I can deploy a new model using an xmla file.

I have tried using Authentication: Microsoft Entra MFA

(I also tried and Microsoft Entra Password but that gave some kind of power bi error)

I am using SSMS:

SQL Server Management Studio@ 20.2.37.0

SQL Server Management Objects (SMO):17.100.40.0+f57178c95d4376485d3f597f2b829bbd6f80fd6f

Microsoft T-SQL Parser:17.2.3.1+46115224c373754fdd41516eaae1386cabc4819e.46115224c373754fdd41516eaae1386cabc4819e

Microsoft Analysis Services Client Tools: 20.0.3.0

Microsoft Data SqlClient (MDS):5.1.5

I have updated all my MSOLAP, AMO, AMOMD drivers to the latest releases found here as the ones I had were older:

https://learn.microsoft.com/en-us/analysis-services/client-libraries?view=sql-analysis-services-2025

I have no idea what to try next.

Help please

ERROR Message:

TITLE: Connect to Server

Cannot connect to asazure://uksouth.asazure.windows.net/xxxxxxxxxxx.

ADDITIONAL INFORMATION:

Unable to obtain authentication token using the credentials provided. (Microsoft.AnalysisServices.AdomdClient)

Response status code does not indicate success: 404 (NotFound). (Microsoft.AnalysisServices.AdomdClient)

BUTTONS:

OK

==================================

Cannot connect to asazure://uksouth.asazure.windows.net/xxxxxxxx.

===================================

Unable to obtain authentication token using the credentials provided. (Microsoft.AnalysisServices.AdomdClient)

Program Location:

at Microsoft.AnalysisServices.AdomdClient.Authentication.MsalAuthenticationHandle.IntegratedWindowsAuthenticationHandle.AcquireTokenImpl(IPublicClientApplication app, IEnumerable`1 scopes, String userId, IAccount account, Boolean isInteractiveLoginAllowed)

at Microsoft.AnalysisServices.AdomdClient.Authentication.MsalAuthenticationHandle.IntegratedWindowsAuthenticationHandle.AcquireToken(IPublicClientApplication app, IEnumerable`1 scopes, String userId)

at Microsoft.AnalysisServices.AdomdClient.Authentication.MsalAuthenticationHandle.MsalAuthenticationService.AuthenticateUser(AuthenticationOptions options, AuthenticationInformation authInfo, String userId)

at Microsoft.AnalysisServices.AdomdClient.Authentication.AuthenticationManager.Authenticate(AuthenticationOptions options, String identityProvider, String resource, String tenantId, String userId, String password, String workspaceName, String databaseName, Boolean isForAsAzureRedirection, AuthenticationInformation& authInfo)

at Microsoft.AnalysisServices.AdomdClient.ConnectionInfo.AcquireToken(IConnectivityOwner owner, String resource, String tenantId, Boolean isForAsAzureRedirection)

at Microsoft.AnalysisServices.AdomdClient.ConnectionInfo.HandleAsAzureRedirection(IConnectivityOwner owner)

at Microsoft.AnalysisServices.AdomdClient.XmlaClient.<>c__DisplayClass73_0.<Connect>b__1()

at Microsoft.AnalysisServices.AdomdClient.Security.TransparentUserContext.ExecuteInUserContextImpl(Action action)

at Microsoft.AnalysisServices.AdomdClient.XmlaClient.Connect(ConnectionInfo connectionInfo, Boolean beginSession)

at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.XmlaClientProvider.Connect()

at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.XmlaClientProvider.Microsoft.AnalysisServices.AdomdClient.AdomdConnection.IXmlaClientProviderEx.ConnectXmla()

at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.ConnectToXMLA(Boolean createSession, Boolean isHTTP)

at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.Open()

at Microsoft.SqlServer.Management.SqlStudio.Explorer.ObjectExplorerService.ValidateConnection(UIConnectionInfo ci, IServerType server)

at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()

===================================

Response status code does not indicate success: 404 (NotFound). (Microsoft.AnalysisServices.AdomdClient)

Program Location:

at Microsoft.AnalysisServices.AdomdClient.Utilities.AsyncHelper.WaitForTaskCompletionImpl(Task task, Int32 timeout, CancellationToken cancelToken)

at Microsoft.AnalysisServices.AdomdClient.Utilities.AsyncHelper.WaitForTaskCompletionAndGetResult

at Microsoft.AnalysisServices.AdomdClient.Authentication.MsalAuthenticationHandle.IntegratedWindowsAuthenticationHandle.AcquireTokenImpl(IPublicClientApplication app, IEnumerable`1 scopes, String userId, IAccount account, Boolean isInteractiveLoginAllowed)

  1. Manoj Kumar Boyini 17,060 Reputation points • Microsoft External Staff • Moderator

    Hi TammyReaume-5087,

    Thank you for sharing the details. The error you’re encountering is a known issue related to older versions of SQL Server Management Studio (SSMS) when connecting to Azure Analysis Services (AAS) using Microsoft Entra authentication.
    This issue is caused by a bug in SSMS 19.x, which affects authentication token acquisition for Azure Analysis Services. The issue has been fixed in later versions of SSMS.

    Follow the Steps

    Step 1: Update SSMS to the latest version
    Please install the latest version of SQL Server Management Studio (SSMS) using the following download link: https://aka.ms/ssmsfullsetup

    SSMS normally installs and updates the required client libraries automatically. However, in some cases, older client libraries may still remain on the system and need to be updated manually.

    Step 2: Verify Azure Analysis Services client libraries
    Please ensure that all Azure Analysis Services client components are up to date on the machine.

    For the MSOLAP (OLE DB Provider), navigate to C:\Program Files\Microsoft Analysis Services\AS OLEDB\ If multiple folders exist, select the folder with the highest version number. Right‑click msolap.dll, select Properties, then go to Details and check the Product version. If the file name is msolap140.dll, this indicates an older version and should be upgraded.

    For AMO (Analysis Management Objects), navigate to C:\Windows\Microsoft.NET\assembly\GAC_MSIL\Microsoft.AnalysisServices\ If multiple folders exist, select the highest version. Right‑click Microsoft.AnalysisServices.dll, select Properties, and review the version under Details.

    For ADOMD, navigate to C:\Windows\Microsoft.NET\assembly\GAC_MSIL\Microsoft.AnalysisServices.AdomdClient\ Again, select the highest version folder if multiple exist. Right‑click Microsoft.AnalysisServices.AdomdClient.dll, choose Properties, and verify the version under Details.

    Step 3: Manually update client libraries if required
    If any of the above client components are outdated, download and install the latest Azure Analysis Services client libraries from the following link: https://learn.microsoft.com/analysis-services/client-libraries

    Hope this helps, Please let us know if you have any questions and concerns.

  2. Manoj Kumar Boyini 17,060 Reputation points • Microsoft External Staff • Moderator

    Hi TammyReaume-5087,

    I hope you had a chance to review the information shared earlier, and I hope this information has been helpful! If you still have questions, please let us know what is needed in the comments so the question can be answered.

Sign in to comment

1 answer

  1. TammyReaume-5087 0 Reputation points

    Thank you for your response but all the suggestions and steps suggested for troubleshooting I had already done as stated in original post.

    However, I have resolved the issue. The issue was the AAS server had been used in 'Analysis Services Migration' in Power BI services and the redirect button had been activated so all login requests were being redirected here. However, the migration never successfully completed so all the errors. We have resolved this now thanks to help via another support case to Microsoft as because of this we were also not able to delete the server instance and rebuild it either.

    Turns out that was the root of all our heartache.

    0 comments No comments
    Sign in to comment
Sign in to answer

Your answer