Analysis Service cube connector does not work with my Azure Service principal

iva rozelin 0

Hi,

I have two Analysis services Cubes - one is built upon DAX while the other is built upon M Code. After I created my Azure service principal, I successfully change the DAX cube connector and it works fine now. However, I try to change the connector to my M Code cube, it does not work. The current connection is DirectQuery. Is there a limitation regarding the connector options for case such as mine? Do you have any idea what might have went wrrong? Any suggestions how to change it?

iva rozelin 0 Reputation points

2023-12-12T15:20:17.7566667+00:00

Additional details: when I enter the user and the password of the service principal it says that it is invalid.
PRADEEPCHEEKATLA 90,236 Reputation points

2023-12-13T02:25:41.2066667+00:00

@iva rozelin - Thanks for the question and using MS Q&A platform.

Could you please share the complete stack trace of the error message which you are experiencing?

Meanwhile, you can check out the Azure Analysis Services Connection Details.
iva rozelin 0 Reputation points

2023-12-13T08:00:52.19+00:00

Hi @PRADEEPCHEEKATLA , actually I dont get an error. The connector itself does not give me the option to choose authentication with Service Principal. I read in the documentation that Service principal authentication is supported for connector provider MSOLEDBSQL19 while my cube connector provider is older provider that MS used to have (my cube is written inn M Code). Is there a way to connect Service principal with an old provider?
PRADEEPCHEEKATLA 90,236 Reputation points

2023-12-15T09:08:24.5033333+00:00

@iva rozelin - Based on the information you provided, it seems that the older provider you are using for your M Code cube does not support Service Principal authentication. Unfortunately, there is no way to connect to your cube using Service Principal authentication with this provider.

However, there are a few workarounds that you can try:

Upgrade to a newer version of the provider that supports Service Principal authentication. You can check if there is a newer version of the provider available that supports Service Principal authentication and upgrade to it. This might require some changes to your cube or other components that use the provider, so make sure to test it thoroughly before deploying it to production.

Use a different authentication method. If Service Principal authentication is not an option, you can try using a different authentication method, such as Windows authentication or SQL Server authentication. This might require some changes to your cube or other components that use the provider, so make sure to test it thoroughly before deploying it to production.

Use a different connector. If none of the above options work, you can try using a different connector that supports Service Principal authentication. For example, you can try using the Analysis Services connector or the ODBC connector. This might require some changes to your cube or other components that use the connector, so make sure to test it thoroughly before deploying it to production.

I hope this helps. Let me know if you have any further questions or concerns.
PRADEEPCHEEKATLA 90,236 Reputation points

2023-12-20T05:08:23.3033333+00:00

@iva rozelin - We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

Share via

Analysis Service cube connector does not work with my Azure Service principal

Your answer