top of page

Securing Your Data: A Guide to Azure OpenAI on Your Data

Leveraging your custom data with OpenAI's large language models through Azure OpenAI on Your Data opens a world of possibilities for AI-powered applications. But paramount to success is ensuring the security of your valuable information. This guide dives into the robust security features of Azure OpenAI on Your Data, empowering you to safeguard your data.

We'll explore how Virtual Networks (VNets) create a secure place for your data. VNets isolate resources and enable granular Data access control, significantly reducing the risk of unauthorized access. Additionally, we'll discuss the power of private endpoints within a VNet. These endpoints further enhance security by restricting inbound traffic and eliminating reliance on the public internet, providing a protective layer for sensitive data.

What is a Virtual Network (VNet)?

In simpler terms, a VNet acts like a private network environment within Azure. It isolates your resources, such as Azure OpenAI services and data storage, significantly enhancing data security by keeping them away from the public internet. This isolation helps to minimize the risk of unauthorized access and potential security breaches.

VNet Architecture and Data Security in Azure OpenAI on Your Data

The diagram depicts a Microsoft Managed VNet, a service to simplify the process by letting Microsoft create and manage the virtual network within your Azure environment. This VNet is the foundation for securing your Azure OpenAI on Your Data deployment, providing a secure place for your data and ensuring its privacy.

Core Component: Microsoft Managed VNet

This core element establishes a logically isolated network environment dedicated to your Azure resources. Imagine it as a private cloud within the broader Azure infrastructure. By isolating resources like Azure OpenAI services and data storage (e.g., Azure Blob Storage) from the public internet, the VNet significantly reduces the attack surface and potential exposure points for unauthorized access attempts.

Your Azure Subscription: This contains the resources you want to use with Azure OpenAI on Your Data.

Azure OpenAI Services: These are the specific Azure OpenAI services that you are using in this case, such as:

  • Azure OpenAI: This service allows you to use OpenAI's large language models for tasks like text generation, translation, and code completion.

  • Azure AI Search: This service allows you to index and search over large amounts of unstructured data.

  • Blob Storage: This is a solution for unstructured data like text and binary data.

  • App Services: This service allows you to host web applications, mobile backends, and APIs in a fully managed environment.

Subnets: Organized Resource Management

Subnets act as logical subdivisions within the VNet, allowing you to organize your Azure resources and control more granularly.

  • Gateway Subnet: Facilitates secure traffic flow between your on-premises network and the VNet.

  • Key Services Subnet: Houses critical Azure services you're using, such as Azure OpenAI and Azure AI Search.

  • Web App Subnet: Specifically designed to accommodate your web application.

Network Navigation

  • DNS (Domain Name System): Translates user-friendly domain names into numerical IP addresses that computers can understand.

  • Private DNS Zones: These internal zones enable domain name resolution specifically within the VNet, adding another layer of security.

Optional Connectivity: Azure VPN Gateway and On-Premises Network

  • Azure VPN Gateway: Provides a secure connection between your on-premises network and the VNet, allowing resources within your local network to communicate securely with Azure resources.

  • On-premises Network: Represents your local network that you might want to connect to the VNet for secure communication.

Advantages of VNet for Azure OpenAI on Your Data

By leveraging a VNet with Azure OpenAI on Your Data, you gain several security advantages:

  • Network Isolation: The VNet inherently restricts access to your resources. Only authorized entities within the VNet can communicate with your data and OpenAI services. This significantly reduces the risk of unauthorized access attempts from the public internet.

  • Granular Data Access Control with Subnets: As mentioned earlier, subnets enable you to define fine-grained access policies for different parts of your Azure OpenAI on Your Data environment. This ensures that only authorized resources can access specific data and services, minimizing the potential for data breaches.

Private Endpoints for Further Security

Imagine a VNet as a secure highway system within Azure. Private endpoints function like dedicated lanes within this network. These endpoints establish private connections between your Azure resources residing in the VNet, allowing them to communicate securely without ever touching the public internet. Think of private tunnels built within your secured highway system (VNet).

Enhanced Security with Private Endpoints

Private endpoints significantly elevate data security within your Azure OpenAI on Your Data environment.

Here's an overview of their security benefits:

  • Reduced Attack Surface: By keeping communication internal to the VNet, private endpoints minimize the attack surface exposed to potential threats on the public internet. Fewer entry points for malicious actors translate to enhanced security.

  • Restrict Inbound Traffic: Private endpoints ensure that inbound traffic originates from authorized resources within the VNet. This significantly restricts access attempts from unauthorized entities lurking on the public internet.

Consider the below image.

The private endpoint creates a secure connection within the VNet for Azure OpenAI's preprocessing jobs API to access data stored in Azure Blob Storage. This eliminates the need for data to flow over the public internet, significantly reducing the attack surface and potential security risks.

Here's how private endpoints contribute to secure communication in Azure OpenAI on Your Data:

  • Restricted Communication Path: By leveraging a private endpoint, communication between Azure OpenAI services and other Azure services (like Azure Blob Storage) occurs entirely within the confines of the VNet. Data never needs to be exposed to the public internet, significantly reducing the risk of unauthorized access or interception [1].

  • Improved Security Posture: By minimizing reliance on the public internet, private endpoints bolster the overall security posture of your Azure OpenAI on Your Data deployment. This is especially crucial when dealing with sensitive data.

Key Points

  • Private endpoints are visualized by dotted blue lines connecting Azure services within the VNet.

  • These connections bypass the public internet, enhancing data security.

  • They restrict inbound traffic to authorized resources within the VNet.

The diagram also highlights that Azure OpenAI service and Blob Storage use managed identities for authentication. Both managed identities and authentication through managed identities provide a robust security posture.

  1. You don't store sensitive credentials within your code, eliminating the risk of accidental leaks or unauthorized access.

  2. Azure manages the identities and permissions, reducing the complexity of managing credentials.

  3. Secure communication between Azure services is facilitated without compromising security.

It's important to remember that private endpoints are an optional security measure. You can configure your Azure OpenAI on Your Data architecture to function without them. However, private endpoints are a recommended best practice for enhanced security, especially when handling sensitive data.


With a comprehensive understanding of these security measures, you can leverage Azure OpenAI on Your Data, empowering you to unlock the transformative potential of AI while safeguarding your valuable data.


bottom of page