Clarification Request: HIPAA Eligibility of Azure OpenAI Realtime API (Audio In/Out)

Wesparcmedia 0 Reputation points
2025-11-10T13:30:25.2666667+00:00

Dear Microsoft Azure Compliance Team,

I’m reaching out to confirm whether the Azure OpenAI Realtime API — specifically the audio-in/audio-out (speech) modality used with models such as gpt-4o-realtime — is covered under Microsoft’s Business Associate Agreement (BAA) for HIPAA compliance.

Context:

The Realtime resource is deployed in East US 2 under my client’s Azure subscription (I am acting as their technical contractor).

We are handling Protected Health Information (PHI) in real-time voice conversations and need written confirmation before enabling the Realtime API in production.

We understand that the Azure OpenAI Service (text) is HIPAA-eligible under the BAA, but we cannot find documentation explicitly confirming that the Realtime audio modality is included in the HIPAA-eligible scope.

Could you please confirm yes or no:

Is the audio streaming modality of Azure OpenAI Realtime API (voice input/output) currently HIPAA-eligible under the Microsoft BAA?

If yes, could you share the documentation link or Product Terms reference that lists this modality as in-scope?

If no, do you have an estimated timeline or roadmap for when it will become HIPAA-eligible?

Please note: although I’m sending this request from my own address, the resource belongs to my client’s Azure tenant. I can provide the Azure Subscription ID : 

88ed7a33-6f6f-431a-b0e8-5d9b3b0da5d9

 Resource Name : real-time-api

Thank you for your assistance and clarification.

Best regards

Foundry Tools
Foundry Tools

Formerly known as Azure AI Services or Azure Cognitive Services is a unified collection of prebuilt AI capabilities within the Microsoft Foundry platform

0 comments No comments

2 answers

Sort by: Oldest
  1. AI answer

    2025-11-10T13:30:47.02+00:00

    The context provided does not explicitly mention the HIPAA eligibility of the Azure OpenAI Realtime API, specifically for the audio-in/audio-out modality. It states that the Azure OpenAI Service (text) is HIPAA-eligible under the BAA, but there is no confirmation regarding the audio streaming modality being included in the HIPAA-eligible scope. Therefore, I cannot confirm whether the audio streaming modality of Azure OpenAI Realtime API is currently HIPAA-eligible under the Microsoft BAA.

    For the most accurate and up-to-date information, I recommend reaching out directly to Microsoft Azure Compliance or consulting the relevant Azure documentation regarding HIPAA compliance and the specific services in question.


    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. SRILAKSHMI C 19,735 Reputation points Microsoft External Staff Moderator
    2025-11-11T13:43:35.6066667+00:00

    Hello Wesparcmedia,

    Welcome to Microsoft Q&A,

    Thank you for reaching out and for providing detailed context around your use case.

    I completely understand the need to confirm HIPAA eligibility before enabling the Azure OpenAI Realtime API for PHI-related workloads.

    Here’s what you need to know:

    1. HIPAA Compliance Overview

    Microsoft supports compliance with the Health Insurance Portability and Accountability Act (HIPAA) through its Business Associate Agreement (BAA). This agreement allows customers who are covered entities or business associates under HIPAA to use in-scope Microsoft services for processing Protected Health Information (PHI).

    However, HIPAA coverage applies only to services explicitly included within the BAA’s compliance boundary. Microsoft publishes these services in its official HIPAA Compliance Scope documentation.

    2. Azure OpenAI Realtime API and Audio Modality

    The Azure OpenAI Service (text-based endpoints) is HIPAA-eligible under the Microsoft BAA and can be used for PHI processing when covered by your organization’s signed BAA with Microsoft.

    That said, the Realtime API (audio-in/audio-out) functionality including live speech input and audio response is still in preview and not yet included in Microsoft’s current HIPAA-eligible scope.

    As a result, this feature should not be used to transmit or process PHI until it is formally added to the list of HIPAA-covered services.

    Microsoft is actively working on expanding compliance coverage for new Azure OpenAI modalities such as the Realtime API. While we don’t have a confirmed timeline for HIPAA inclusion, any updates will be reflected in the official:

    Azure OpenAI Documentation

    For production workloads involving PHI, we recommend continuing to use the text-based Azure OpenAI API, which is already covered under the BAA, or waiting until the Realtime API is formally listed as HIPAA-eligible.

    I Hope this helps. Do let me know if you have any further queries.


    If this answers your query, please do click Accept Answer and Yes for was this answer helpful.

    Thank you!

    Was this answer helpful?


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.