Azure Stream Analytics Virtual Network Integration Goes GA!

We are thrilled to announce that the highly anticipated capability of running your Azure Stream Analytics (ASA) job in an Azure Virtual Network (VNET) is now generally available (GA)! This feature, which has been in public preview, is set to revolutionize how you secure and manage your ASA jobs by leveraging the power of virtual networks.

What Does This Mean for You?

With VNET integration, you can now lock down access to your ASA jobs within your virtual network infrastructure. This provides enhanced security through network isolation, ensuring that your data remains protected and accessible only within your private network. By deploying a containerized instance of your ASA job inside your VNET, you can privately access your resources using:

• Private Endpoints: These allow you to connect your VNET-injected ASA job to your data sources privately via Azure Private Link. This means that your data traffic remains within the Azure backbone network, reducing exposure to the public internet and enhancing security.
• Service Endpoints: These enable you to connect your data sources directly to your VNET-injected ASA job. This simplifies the network architecture by providing direct connectivity.
• Service Tags: These allow you to manage network security by defining rules that allow or deny traffic to Azure Stream Analytics. This helps in maintaining a secure environment by controlling which services can communicate with your ASA jobs.

Overall, VNET integration enhances the security of your ASA jobs by leveraging Azure's robust networking features.

Expanded Regional Availability

We are also excited to announce that this capability is now available in additional regions! Along with the existing regions (West US, Central Canada, East US, East US 2, Central US, West Europe, and North Europe), you can now enable VNET integration in the following regions:

• Australia East
• France Central
• North-Central US
• Southeast Asia
• Brazil South
• Japan East
• UK South
• Central India

These regions were added in response to customer feedback. If you have suggestions for additional regions, please complete this form: https://forms.office.com/r/NFKdb3W6ti?origin=lprLink

This expansion ensures that more customers around the globe can benefit from the enhanced security and network isolation provided by VNET integration.

Getting Started

To get started with VNET integration for your ASA jobs, follow these steps:

1. Set Up Your VNET: Create or use an existing Azure Virtual Network.
2. Create a Subnet: Add a dedicated subnet for your ASA job within the VNET.
3. Set Up Azure NAT Gateway or disable outbound connectivity: Enhance security and reliability by setting up an Azure NAT Gateway or disable default outbound connectivity. 
4. Associate a Storage Account: Ensure you have a General Purpose V2 (GPV2) Storage account linked to your ASA job.
5. Configure Your ASA Job:
   • Azure Portal: Go to Networking and select "Run this job in virtual network." Follow the prompts to configure and save.
   • Visual Studio Code: In the 'JobConfig.json' file, set up the 'VirtualNetworkConfiguration' to reference the subnet.
6. Check Permissions: Make sure you have the necessary Role-based access control permissions on the subnet or higher.

For detailed instructions and requirements, refer to the official documentation Run your Stream Analytics in Azure virtual network - Azure Stream Analytics | Microsoft Learn.

Join the Revolution

Stay tuned for more updates and exciting features as we continue to innovate and improve Azure Stream Analytics. 

Our other Ignite releases include Azure Stream Analytics Kafka Connectors is Now Generally Available!

If you have any questions or need assistance, feel free to reach out to us at askasa@microsoft.com.

Happy streaming!