Present Azure Analysis Services on a VNET
Instead of making Azure AS available on the internet, allow admins to move it so it's only available on a VNET.
Looking into it. Thanks.
Any word on this? I'm guessing this one won't happen, despite how badly we need it. I think you should go thru the remaining requests for AAS and just "complete" them all so we won't keep voting on them.
I think the preferred phrasing is that "the investment is happening in the Power BI superset of AAS." (IE. these requests *are* being completed, but just in a totally different product)
It seems unfortunate that Microsoft cannibalizing this PaaS platform for a much more costly and immature SaaS offering. Our Microsoft consulting partners advised us to adopt AAS just one year ago and now that we have a solution in production, we are starting to realize that AAS is a sinking ship.
This would be a nice feature to have, otherwise allowing a Private Endpoint to connect to the AAS would do the trick for me. But it looks like things aren't going as planned considering the lack of updates, hopefully everything will be sorted out soon enough.
Daniel Shanks commented
Please could you look a bit faster? Thanks
Martin Huba commented
Well, that "look" is astonishingly long one.
Erwin de Kreuk commented
This is really becoming a necessary option. Almost all services in a Modern Data Estate can use Vnet Integration and Private EndPoints, but AAS cannot. Is this already on the roadmap
Jeroen Schalken commented
It is now working with the workarround of creating an on-premises data gateway. This seems unnecessary costly and inefficient when connecting to e.g. an Aure SQL database. Still waiting for the possibility to have a direct connection on a VNET?
Do we have any apporx. date by when the VNET support will be available for Azure Analysis Services?
To make it worse, AAS do not have static IP address range as well, right?
Any update on this.
Pawel Wenda commented
VNET endpoint is must have for any Enterprise architecture. I know I get use gateway hosted on VNET but with TB-PB of data this is super inneffective and requires additional scale sets of VMs for every AAS. Please prioritize this.
Any update on this?
VNET tunneling is on the backlog, but there are dependencies for Azure AS to talk to other cloud services on the VNET. We don't have timeline for this yet.
However, we are implementing a feature that will be ready soon, which will provide a workaround. We will create a property on an Azure AS server to always go through a gateway to get data - including cloud sources such as Azure DW, etc. If the gateway machine is in the VNET, it is not necessary to open up access on the data sources for Azure AS.
Firewall is already done to prevent user access.
Do we have any update on this please?
Any update on this? i have a database on a vnet and a Azure SSAS i can deploy the SSAS outside the vnet but it fails because it cannot connect to the DB or i can connect to the vnet and access the DB but cannot access the Azure SSAS