Hello,
There are certain ways to use Open AI with DLP. i am listing couple of those here :-
- Sensitive Data Handling:
- When DLP is enabled, Azure OpenAI Service ensures that sensitive information (such as personal identifiable information or confidential business data) is not leaked through any network requests. By restricting outbound access to only approved destinations (via
allowedFqdnList
), you ensure that even if an external service or API is used during the processing, it is only one you explicitly trust.
- When DLP is enabled, Azure OpenAI Service ensures that sensitive information (such as personal identifiable information or confidential business data) is not leaked through any network requests. By restricting outbound access to only approved destinations (via
- Communication with External Resources:
- If your Azure OpenAI deployment is designed to call other services or APIs (for example, calling a database or an external service during model execution), the outbound traffic must be restricted to known, authorized endpoints. This ensures no unintended exposure of data to external, possibly untrusted, services.
- The
allowedFqdnList
configuration would typically include FQDNs of other Azure services or trusted third-party services that the OpenAI Service might need to communicate with. For example, if your deployment needs to call a specific API to process or retrieve some information, the FQDN of that API must be added to this list.
- Data Ingress and Egress:
- Data that enters (ingress) and leaves (egress) your environment via Azure OpenAI Service is filtered by the DLP controls. By restricting egress traffic, DLP prevents potential leakage of sensitive data that may result from API calls to external, unapproved destinations.
- In addition, all data passed to and from the OpenAI service via API calls can be subject to monitoring and logging for compliance and security auditing, depending on your Azure configuration.
Regards
Rahul
Microsoft Customer Support