Scenario
I have a cube (tabular model)
It contains a list of Customers, and a measure Revenue.
The Customer table has a column Client Account Manager.
I will have a report which points to this default perspective, and the Security Role will apply Row Level Security showing only the Client Account Manager their Revenue, for their Customers. Simple.

For Account Managers & Non-account managers, I also want them to be able to see the revenue for any Customer, even if it is not their own, but I don’t want them to be able to write a report (or remove a filter), and sum the Revenue for each of the Client Account Managers.

I only ever want them to be able to return 1 Customer at a time. (I realize if they ran the report for all 20 customers an Account Manager manages they could do the sums themselves)

So, I can’t see how to do this now, but if I had the following enhancement, it would allow me to use the same cube, with different perspective.

I want to create a perspective on the same cube, without Client Account Manager Column. So, the user cannot select this field.
Given I only ever want them to be able to see 1 customer at a time a Perspective Level Required Filter would enable this for me, without the need to build a second cube.

When an Azure Analysis Services instance is Paused, any deployment of an Azure Resource Manager Template that includes the Azure Analysis Services instance fail with the error "The server is currently being updated. Please try again later.".

This happens even if the exact same configuration is applied to the Azure Analysis Services instance and has the potential to break CI/CD pipelines as a result.

Azure should allow Analysis Services to be "updated" by Resource Manager Templates while in the Paused state for configuration that is not dependent upon a running instance.

Other Azure resources like Stream Analytics and Synapse Analytics allow this exact scenario.

If we deploy a LoadBalancer resource, and a LoadBalancer alert rule via ARM template – that rule gets automatically disabled by Azure because the table doesn’t exist yet (until the probe state changes, or some other resource writes to AzureDiagnostics), causing the query in the alert rule to have a syntax error - then, when the probe state does * change due to an error condition, the alert won’t be triggered because the alert rule has been auto-disabled by Azure. Azure auto-disables alert rules when there is a query syntax error. Give the user a choice to elect * this auto-disabling behavior, or to *decline * it. Azure does this to help the subscriber save cost; but it could be far more costly to miss an alert, due to Azure auto-disabling alert rules

In the past with SSAS you could use Windows Authentication in your connection and send your excel file to other users and they could refresh

With AAS this is not possible as you have to put your login in the connection string which is very unfriendly

I thought this guide might help https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/analysis-services/analysis-services-odc.md and initially it does seem work for asazure:// protocol, but it doesn't work for link:// protocol which we have employed

I posted this feedback on that page and was told to post this here.

Please can you extend this capability to work with the link:// protocol.

Right now excel isn't practical on AAS with MFA as it prevents users sharing their workbooks due to having to set the username limitation.

https://docs.microsoft.com/en-us/azure/analysis-services/analysis-services-server-alias

If I use the asazure:// protocol the odc works but if I switch it to the link:// protocol I get the error "Initialization of the data source failed..."

I guess it is some limitation of the javascript but I don't really know what it is doing to adapt it