Overview of Zoom and Microsoft integrations by surface
| Explainers | Explainers are scannable resources designed to make Zoom’s products easier to understand. By blending the structure of an FAQ with some elements of a whitepaper, these documents break down technical concepts into short summaries and fuller explanations. Each section header delivers a quick takeaway, while the accompanying content offers clarity for those seeking more depth. | /files/SEMj0Jx14DA7tLxZm76P |
| Field Guides | Field Guides act as navigation tools and deployment guides for Zoom products and features. These documents focus on helping IT admins complete complex tasks or processes, like deploying the Zoom Phone Local Survivability Module or configuring advanced Zoom Contact Center features. Within these documents, you can expect clear, step-by-step instructions and practical tips that streamline implementation and support successful, organization-wide deployments. | /files/6z06gQu6dZtVa2OIRKAW |
| Bluepapers | Bluepapers, named after Zoom’s signature color, serve as in-depth strategic resources that expand on standard whitepapers. These documents explore entire product lines or services—like Zoom Phone and Zoom Contact Center—with comprehensive overviews, key insights, and summaries of essential topics. Ideal for gaining a complete understanding, Bluepapers serve as a go-to resource for deep insight into Zoom's products. | /files/MvzSLh5Ei2cnbi5YSppj |
Overview of Zoom and Microsoft integrations by surface
Meetings
Zoom Whiteboard
Zoom Phone
Chat and Notifications
Core Calling and Routing
Enterprise Telephony Management
Voicemail, Recording, and Transcription
Messaging and Caller Controls
An overview of Zoom's AI Service Models: Federated, ZM+, and ZMO
Diagram illustrating Zoom's federated approach
Diagram illustrating Zoom's ZM+ approach
Diagram illustrating Zoom's
Zoom-Hosted Models Only approach
Live captions in a meeting
Translated captions in a meeting
The AI Chat panel
Prompting Zoom AI to summarize Zoom Chat Messages for Next Steps
The output of the previous prompt
Summarizing a multi-comment thread into one paragraph.
Summary of a document uploaded to Zoom Chat
Speaker biography generation prompt
Output of the previous prompt
Event image generation prompt and output
The generated image featured on the Events page
Zoom Events Email Compose prompt
Output of the previous prompt
Zoom Events Smart Compose prompt in the Lobby
Output of the previous prompt
Smart upload interface
Illustration of generative content options
Options for refining generative content
Email Compose generating an email based on the user prompt without previous context
Email Compose generating an email based on the user prompt with the email thread's context
Zoom AI summarizing an email
Meeting Questions answering user questions
Example of Meeting Summary
Meeting Summary converted to a Zoom Canvas Doc
Example of Smart Recording
A Zoom Phone Call Summary and Next Steps.
The creation of a voicemail prioritization Intent.
Identified Zoom Tasks and Voicemail Prioritization
A Zoom Phone SMS exchange between an agent and customer
A summary of the pervious conversation
Opening a Zoom Canvas doc from a call summary
Asking questions during a live phone call
Automatically identified Tasks awaiting acceptance
Data flows for My Notes within a Zoom meeting.
Data flows for My Notes outside of a Zoom meeting.
The ZoomMate work surface
A conversation prompting Advanced Mode
Example of building a Workflow using natural language prompting
The custom avatar clip creation interface
Adding words to a custom dictionary
Example of a new custom template
Example of a a Zoom Canvas doc using text and data tables
Example of a Zoom Paper doc in standard template with a college lesson plan
Example of a Zoom Sheets doc
Example of Zoom Slides, showcasing AI-generated slides
A simple overview of Zoom AI
Overview of Zoom's AI approaches, including Federated, ZM+, and ZMO
Overview of how live media is transformed into speech-to-text data that powers Zoom AI features
Overview of how Zoom processes recordings and AI features
Overview of how Zoom processes derivative AI content generation features
Overview of how Zoom processes generative and composition AI requests
Overview of My Notes data flows in Zoom meetings
Overview of My Notes data flows outside of Zoom meetings
Overview of ZoomMate data flows
Overview of how ZoomMate connects to third-party connections and data sources
Overview of the Custom Avatar creation process
Overview of the Custom Avatar clip creation process
Custom Dictionary data flows
Custom Meeting Summary Templates data flows
Overview of how Personal Audio Isolation isolate's a user's voice
| Product | AI Feature | Federated | ZM+ | ZMO |
|---|---|---|---|---|
| Chat | Chat Compose Draft messages based on conversational context and what you want to say, as well as customize its tone and length. | ✔️ | ✔️ | ✔️ |
| Chat | Message, Thread and Doc Summary Quickly summarize the content of long Chat threads, messages, and attached documents. | ✔️ | ✔️ | ✔️ |
| Clips | Custom Avatars Creates a personalized avatar from a user's recorded video and voice for generating avatar-based clips. | ✔️ | ||
| Clips | Smart Tags Create clip titles, descriptions, and tags. | ✔️ | ✔️ | ✔️ |
| Events | Chat Compose Draft chat messages for your Lobby chat based on conversational context and what you want to say, as well as customize the tone and length. | ✔️ | ✔️ | ✔️ |
| Events | Content Generation Use AI to generate written event content such as descriptions, session details, speaker bios, and lobby announcements. | ✔️ | ✔️ | ✔️ |
| Events | Email Compose Generate an email, subject lines, titles, and calls to action, using context from your Zoom Event description and/or providing a more specific prompt. | ✔️ | ✔️ | ✔️ |
| Events | Image Generation Generate unique images to use in your event. | ✔️ | ✔️ | |
| Events | Smart Compose Write compelling event content when setting up an event including event description, session descriptions, speaker bios, lobby announcements, images, and more. | ✔️ | ✔️ | ✔️ |
| Mail and Calendar | Email Compose Compose and reply to emails faster with suggested content based on the email thread and what you want to say. | ✔️ | ✔️ | |
| Mail and Calendar | Email Summary Quickly summarize the content of emails. | ✔️ | ✔️ | |
| Meetings | Meeting Questions Quickly catch up and get clarity on what you missed during a meeting without interrupting it. | ✔️ | ✔️ | ✔️ |
| Meetings | Meeting Summary Generate a summary and next steps of what was discussed in your meetings and share through email and Chat. | ✔️ | ✔️ | ✔️ |
| Meetings | Smart Recordings Review cloud recordings faster through highlights, smart chapters, summaries, and next steps, and get analytics on key meeting and conversation factors. | ✔️ | ✔️ | ✔️ |
| Meetings | Virtual Background Generation Choose the best backdrop with AI-generated virtual backgrounds. | ✔️ | ||
| My Notes | My Notes Capture personal notes, transcript-based context, and meeting details to support later review, follow-up, and AI-assisted work. | ✔️ | ✔️ | ✔️ |
| Phone | Call Questions UsesAI to answer questions about an active or completed phone call using the call's speech-to-text data as context. | ✔️ | ✔️ | ✔️ |
| Phone | Call Summary Generate a call summary of what was discussed in your phone call conversation to gather information important to you. Edit and share it as you see fit. | ✔️ | ✔️ | ✔️ |
| Phone | Create Canvas Doc Create a Zoom Canvas document from a call summary, including key discussion points, next steps, and action items. | ✔️ | ✔️ | ✔️ |
| Phone | SMS Thread Summary Summarize your SMS threads as a member of a call queue or auto receptionist to quickly generate your responses. | ✔️ | ✔️ | ✔️ |
| Phone | Voicemail Prioritization Quickly prioritize your voicemails using topic or intent. | ✔️ | ||
| Phone | Voicemail tasks Quickly access a summarized list of tasks from your voicemail transcription. | ✔️ | ✔️ | ✔️ |
| Productivity | Zoom Canvas Use AI to generate and revise content. | ✔️ | ✔️ | ✔️ |
| Productivity | Zoom Paper Use AI to generate and revise content. | ✔️ | ||
| Productivity | Zoom Sheets Use AI to generate and revise content. | ✔️ | ||
| Productivity | Zoom Slides Use AI to generate and revise content. | ✔️ | ||
| Tasks | Recommended Actions Provides AI-suggested next steps to help users manage and complete tasks more effectively. | ✔️ | ✔️ | |
| Tasks | Task Creation Creates tasks from meeting summaries or other supported Zoom content to help users track follow-up work and responsibilities. | ✔️ | ✔️ | |
| Webinars | Webinar Questions Answers questions about a live webinar using the session's speech-to-text data as context. | ✔️ | ✔️ | ✔️ |
| Webinars | Webinar Summary Generates a structured summary of a webinar's key discussion points, takeaways, and follow-up information after the session ends. | ✔️ | ✔️ | ✔️ |
| Whiteboard | Content Generation Generate ideas, refine and extend existing content, and add objects to a canvas. | ✔️ | ✔️ | ✔️ |
| Whiteboard | Image Generation Generate ideas, refine and extend existing content, and add objects to a canvas with just one click. | ✔️ | ||
| Workplace | AI Chat Panel Send prompts and receive tailored responses sourced from different data sources and contexts available to you. | ✔️ | ✔️ | ✔️ |
| Workspace Reservation | Workspace Recommendations Provides AI-based suggestions for rooms, desks, or in-office days to help users collaborate more effectively. | ✔️ | ✔️ | |
| Zoom Hub | Ask Questions Use AI to answer questions based on selected documents and materials available in Zoom Hub | ✔️ | ✔️ | |
| ZoomMate | AI Agent AI agents that can answer questions, coordinate tasks, and take action across Zoom and connected systems through a conversational agent experience. | ✔️ | ||
| ZoomMate | Custom Dictionary Improve captions, transcripts, and summaries by helping Zoom recognize organization-specific words, abbreviations, and jargon more accurately. | ✔️ | ||
| ZoomMate | Custom Meeting Templates Generate meeting summaries using administrator-defined or user-defined templates that apply a preferred structure, format, or emphasis to the final output. | ✔️ | ||
| ZoomMate | Data Connectors Connect ZoomMate to external applications and data sources so it can retrieve information from, or take action within, connected third-party systems. | ✔️ | ||
| ZoomMate | Deep Research Conduct more thorough, multi-step research across available sources to produce a richer and more detailed answer. | ✔️ | ||
| ZoomMate | Web Search Search the public web to bring current external information into ZoomMate responses when relevant to the user's request. | ✔️ | ||
| ZoomMate | Workflows Automate recurring tasks using natural-language instructions, scheduled triggers, or event-based logic to reduce manual follow-up work. | ✔️ |
In-meeting indicator that Zoom AI features are enabled
The message a host receives when a participants
requests to disable Zoom AI
The unilluminated icon shows Zoom AI features are not enabled.
In-meeting indicator showing transcription is active
Example of the My Notes pencil icon
My Notes icon indicating My Note is active in the meeting
The message a host receives when a participant requests to
stop transcription
Banner indicating transcription was disabled by the host.
Example of a chat channel profile card with an AI Agent
| User Features | |
|
|
Diagram of a SIP zone's active-active architecture.
Diagram of Zoom's data center redundancy design.
| Zoom Phone User Features | Zoom Phone Administration Features | Audio Prompt Language Support |
|---|---|---|
|
|
|
Example of Zoom Phone licensing.
Example of different Zoom Phone call flows.
Diagram showing data flow and secure port connections.
Diagram of Zoom Phone Cloud Peering Network Design.
Diagram of Zoom Phone Premises Peering Network Design.
| Zoom Phone Basic | Zoom Phone Licensed and Pro | Zoom Phone Common Area |
|---|---|---|
|
|
|
Example of the Zoom Phone integration with Salesforce.
Example of the Zoom Phone integration with Microsoft Teams.
Diagram of possible Auto Receptionists flows.
| Auto Receptionist can route to: | Customizable Auto Receptionist Settings: |
|---|---|
|
|
Diagram of possible IVR flow.
| Forward Calls to: | Leave Voicemail to: |
|---|---|
|
|
Diagram of possible Call Queue flows.
| Call Queue Settings | Customizable Policy Settings |
|---|---|
|
|
Diagram of a Shared Line Group configuration.
| Settings available for an Shared Line Group include: | Customizable Policy Settings: |
|---|---|
|
|
Diagram of Group Call Pickup flow.
Example Call Routing Design.
Example image of the new user profile setup for Zoom Phone.
Example of a call summary.
Example of Tasks extracted from a voicemail.
Example of what the dialog box used to create Voicemail prioritizations.
Example of an SMS thread.
Example of an SMS thread summary.
| Analytics | User Experience |
|---|---|
|
|
Example of Real-Time Analytics Dashboard.
Example of Auto Receptionist Reporting Dashboard.
Example of Team SMS Historical Reporting Dashboard.
Example of the User Performance Reporting Dashboard.
Example of the Feature Entitlement and Membership Reporting Dashboard.
Example of teh Zoom Phone Recording Reporting Dashboard.
Example of the Access Reports Dashboard.
Example SMS templates.
Example of call transcription.
Example of phone lines available to the user.
Example of SMS messages.
Example image of the tabs in Zoom Phone settings on the web portal.
Example image of the Recording tab in the Zoom Phone settings in the Web Portal.
| Zoom Phone | Zoom Phone with Customer Engagement Pack Add-On | Contact List |
|---|---|---|
|
|
|
| Licenses | Calling Plans | User Information |
|---|---|---|
|
|
|
| User: | Call Queue: |
|---|---|
|
|
Example of the Quality of Service tab in the Zoom Phone dashboard.
| List of Calls: | Call Data, including: |
|---|---|
|
|
Example call data.
Example of the Usage and Adoption tab in the Zoom Phone Dashboard.
Example of the Phones and Devices tab in the Zoom Phone Dashboard.
Example heatmap pf devices.
Example SBC tab in the Zoom Phone Dashboard.
Example Emergency Tracking tab in the Zoom Phone Dashboard.
Example Spam tab in the Zoom Phone Dashboard.
Example diagram of ZPLS in a single Site Design while Zoom Phone is inaccessible.
Example diagram of ZPLS in a multi-Site Design while Zoom Phone is inaccessible.
Example diagram of ZPLS in a multi-Site Design with a PSTN while Zoom Phone is inaccessible.
Diagram containing network ports and data flows used within a ZPLS model and an SBC configuration.
Diagram showing BYOP Network design.
Image of the acknowledgement statement regarding usage billing.
Example Phone Test using the Network Connectivity Tool.
Image of the location of the Phone Test.
| Zoom Phone India | Zoom Phone India | Zoom Phone India | ||
|---|---|---|---|---|
| Key Comparisons | Foreign-Hosted PBX | BYOC | Provider Exchange | Native |
| India-Based Data Centers | ❌ | ☑️ | ☑️ | ☑️ |
| Payment In Indian Rupee | ❌ | ☑️ | ☑️ | ☑️ |
| Payment in Global Currency | ☑️ | ❌ | ❌ | ❌ |
| OSP-Registered Business | ☑️ | ☑️ | ☑️ | ☑️ |
| Non-OSP Registered Business | ❌ | ☑️ | ☑️ | ☑️ |
| India-Based Fixed-Line Numbers (Requires MPLS) | ☑️ | ☑️ | ☑️ | ❌ |
| India-Based Mobile Numbers (Does not require MPLS) | ❌ | ☑️ | ☑️ | ☑️ |
| Zoom Contact Center | ☑️* | ☑️ | ☑️ | ❌ |
| Connectivity | MPLS Only | Internet or MPLS† | Internet or MPLS† | Internet or MPLS |
| Zoom Phone India | Zoom Phone India | Zoom Phone India | ||
|---|---|---|---|---|
| Feature | Foreign-Hosted PBX | BYOC | Provider Exchange | Native |
| Short Messaging Service (SMS) | Non-Indian Numbers | ❌ | ❌ | ❌ |
| Phone Number Port-In | Non-Indian Numbers | ❌ | ❌ | ❌ |
| Assign Multiple Numbers to Agent | ☑️ | ☑️ | ☑️ | ❌ |
| End-to-End Encrypted Calls | ☑️ | Conditional | Conditional | ❌ |
| Requirement | Description |
|---|---|
| Business Addresses | A business address is required to validate the location (i.e., city) from which the account will use Zoom Phone services. The address must be supported by valid documentation. |
| Compliance Address | A compliance address is required to verify the physical business location associated with the purchase and use of Zoom-issued mobile numbers. A compliance address may also serve as a business address. |
| Documentation | Includes: Proof of identity for the authorized signatory (Aadhaar, PAN, or government-issued ID) Passport-sized photo and authorization letter Authorized signatory contact details (name, email, phone) Company incorporation certificate or charter documents Proof of business address (utility bill, lease, or similar) GST, company PAN, and TAN registration details Billing address matching compliance address |
| Authorized Representative KYC | Authorized signatories are now subject to end user–level eKYC during CAF signing — ID card validation, live photo and video capture, and real-time facial match verification. |
| CAF and Signature | Zoom compiles the documentation into a customer application form (CAF). The authorized signatory must digitally sign the CAF with an approved digital signature certificate (DSC) after successful eKYC verification. |
| Physical Verification | DoT mandates physical verification every six months, performed by Zoom’s vendors (Hello Verify or On-Grid) using GPS tagging and timestamped evidence. |
| Retention and Audit | Signed CAFs and verification records are stored by Zoom for DoT auditing and may be subject to additional revalidation during regulatory review. |
| Requirement | Description |
|---|---|
| Applicability | All end users assigned Zoom India mobile numbers must complete KYC before activation. |
| Verification Partner | KYC is completed via Zoom’s partner (Equal SDK), with real-time verification through government databases. |
| Accepted Proofs | Aadhaar (via DigiLocker) or driver’s license. |
| Verification Process | Users must provide live photo and video capture in addition to ID type, number, name, and address. ZVC India validates the ID against the live photo for match verification. |
| Location Validation | IP-based location is verified before starting KYC; if the IP is outside India, KYC cannot proceed. |
| Re-KYC Triggers | Required when: ID and live photo do not match. DoT initiates audit. |
| Address Requirement | Users must enter an Indian address but do not need to upload proof-of-address documents. |
| Outcome | Once approved, users gain full PSTN capability; without KYC, only extension-to-extension calling is permitted. |
| Validity | KYC validity is continuous but subject to re-KYC events as defined by DoT circulars. |
| Regulatory Reporting | Zoom shares user-number mappings with the DoT, including both active and inactive numbers. |
| Requirement | Description |
|---|---|
| Business Addresses | A business address is required to validate the location (i.e., city) from which the account will use Zoom Phone services. The address must be supported by valid documentation. |
| Documentation | Must submit proof of business registration (e.g., certificate of incorporation, GST, PAN, TAN), authorized signatory ID, authorization letter, and address proof. |
| Regulatory Obligations | Customers must self-maintain compliance with India’s DoT regulations, including MPLS connectivity and location sharing. |
Example of a threaded team SMS conversation
Example of a threaded team SMS conversation summary
8 CPU
16 GB RAM
80 GB HDD
|16 CPU
16 GB RAM
80 GB HDD
| | **Total Registrations** | 2000 | 5000 | | **Maximum Concurrent Calls** | 240 | 480 | | **Calls Per Second** | 2 | 4 | | **Registrations Per Second** | 60 | 400 | {% hint style="info" %} If the number of endpoints within a survivability-enable site exceeds a site’s deployment capabilities, the ZPLS module will process registrations on a first come, first served basis. Customers are advised to add additional modules, or use the Zoom Phone Policy setting [**Local Survivability Mode**](#_ah8xua8wdq10) to prioritize which users support survivability failover. {% endhint %} ### Module Scaling and Resiliency #### ZPLS modules support clustering for additional scaling and/or resiliency Customers can group ZPLS modules together with up to 20 modules per-site (or 100 total Node devices per-account) for additional redundancy or scaling. {% hint style="info" %} This feature is current in beta and requires a technical support ticket to be enabled. {% endhint %} #### Scaling increases a site’s supported device capabilities Expanding the number of ZPLS modules enhances the capabilities of each site linearly for every additional module. For example, if one module supports a total of 5,000 registrations, deploying five modules will elevate the support to 25,000 registrations. #### Redundancy adds additional modules for resiliency, but does not scale a site’s device capabilities When a ZPLS module is utilized for redundancy purposes, the redundant modules do not contribute to the total number of supported extensions. Instead, the modules are on “hot standby,” and will only engage if primary modules fail. For example, one primary and one redundant module support a total of 5,000 registrations, so if a primary module fails, the redundant module is not oversubscribed with devices beyond its supported limit. #### Example of Deploying ZPLS with Scaling and Redundancy For convenience, the following example demonstrates deployment with additional scaling and redundancy. {% hint style="success" %} **Example**: A hospital is required to support up to 10,000 registered extensions for survivability. To achieve this, the hospital is deploying four ZPLS modules. The first two modules are capable of supporting 5,000 registrations each, resulting in a total capacity of up to 10,000 registrations. However, recognizing the importance of resiliency, the hospital is also deploying two additional modules as redundant backups to the primary modules. In this scenario, the hospital now has primary and secondary survivability hardware deployed. Now, if a primary module encounters a failure, the redundant module(s) will take over to maintain uninterrupted service, while continuing to support up to 10,000 registered devices. {% endhint %} ### Site Design Considerations #### Sites group Zoom Phone users together by location for common telephony settings and policies A **site** is a specific term used within Zoom Phone that groups users with shared characteristics — like a common access code, address, SIP Zone, department, or policies — into a single, manageable group within the Zoom web portal. For some customers, a single site may represent all users within their business, and can span multiple buildings within a campus or location; for others, multiple sites may be required depending on your business needs. For more information on sites or site management, [refer to Zoom’s support center](https://support.zoom.com/hc/en/article?id=zm_kb\&sysparm_article=KB0069716). #### Zoom Phone supports single-site and multi-site designs There are two primary designs for configuring Zoom Phone sites within an account: 1. **Single-site**: Representing all users within an account, potentially spanning multiple buildings or locations, within a single Zoom Phone site. 2. **Multi-site**: Representing segments of users by location, building, department, or function separately, each with their own site.
|
|
North America
Latin America
Asia-Pacific
| EMEA
|
| Zoom Presence | Microsoft Teams Presence |
|---|---|
| On a call | In a Call |
| In a Zoom Meeting | In a Call |
| Presenting | Presenting |
| Available | Available |
| In a calendar event | Busy |
| Do Not Disturb | Do Not Disturb |
| Busy | Busy |
| Away | Away |
User.Read
Allows users to sign in to the app. It also allows the app to read basic company information of signed-in users.
User authentication and basic profile access (UserId, Name, Surname).
User.ReadBasic.All
Allows the app to read a basic set of profile properties of other users in your organization on behalf of the signed-in user. This includes display name, first and last name, email address, and photo.
Organizational contact search and basic user information (UserId, Name, Surname, Email).
Chat.Read
Allows an app to read 1-on-1 or group chat threads, on behalf of the signed-in user.
Read member lists when scheduling calls from chat contexts.
Does not read actual chat messages.
Calendars.ReadWrite.Shared
Schedule Zoom meetings on shared or delegated calendars.
Contacts.Read
User.Read.All
Read user's profile for basic information about the user (Name, Surname, Email, Locale, Phone Number).
Search user's phone number to make a phone call.
| | **Presence.Read.All** | Allows the app to read presence information of all users in the directory on behalf of the signed-in user. Presence information includes activity, availability, status note, calendar out-of-office message, timezone, and location. | Get the presence of a Microsoft contact. | |Place.Read.All
Allows the app to read your company's places (conference rooms and room lists) for calendar events and other applications, on behalf of the signed-in user.
Used to obtain room data for scheduled meetings. If the room data exceeds 200, you must authorize the Place scope to obtain all rooms. This is a Microsoft restriction.
ChatMessage.Send
ChatMember.ReadWrite
Chat.ManageDeletion.All
TeamsAppInstallation.ReadWriteSelfForChat
For CMC feature: BI-Sync Zoom meeting chat and Microsoft Teams group chat.
If Zoom meeting chat member hasn't logged in to the Zoom app in Teams, we will use bot to sync the member's Zoom meeting message to Teams.
| | **Chat.ReadWrite** | Allows an app to read and write 1 on 1 or group chats threads, on behalf of the signed-in user. | For CMC feature: BI-Sync Zoom meeting chat and Microsoft Teams group chat. | \\ #### Presence Synchronization Requirements This section covers the specific permissions required for bi-directional Presence sync for Zoom Phone and Microsoft Teams, and why the **Presence.Read.All** is insufficient. The core permissions deal with presence specifically, while the supporting permissions provide key details that tie into presence, such as matching user identity and phone numbers. Without the additional presence permissions, there can be no bi-directional sync, and presence in Microsoft Teams will not update. **Core Permissions:** * **Presence.Read.All** - Reads Microsoft presence status for synchronization with Zoom Phone * **Presence.ReadWrite** - Updates Microsoft Teams presence based on Zoom activity (bi-directional sync) **Supporting Permissions:** * **User.ReadBasic.All** - Correlates presence data with user identities across systems * **User.Read.All** - Ensures comprehensive user matching and phone number correlation **Technical Implementation Notes** Microsoft Graph Presence Resources: * **GET permissions** - **Presence.Read.All** enables optimized batch retrieval of presence status via Microsoft Graph GET operations * **SET permissions** - **Presence.ReadWrite** enables updating Microsoft Teams presence status via Microsoft Graph SET operations For detailed technical specifications, refer to the [Microsoft Learn article on presence resource type](https://learn.microsoft.com/en-us/graph/api/resources/presence?view=graph-rest-1.0), specifically **GET** and **SET** permissions. **Permission Scope Limitations:** * Presence sync permissions are isolated from other Microsoft Teams functionality * Calendar, chat, and meeting permissions operate independently * Each permission is used only for its stated purpose #### Security and Compliance **Data Access Principles:** * **Least Privilege** - Each permission requested only when required for specific functionality * **Purpose Limitation** - Permissions are used solely for the stated Zoom integration purposes * **User Consent** - All permissions require explicit administrative consent during setup, unless customer allows user-based consent (more information can be found in [Microsoft’s Application Consent article](https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/configure-user-consent?pivots=portal#configure-user-consent-in-microsoft-entra-admin-center)) * **Data Minimization** - No cross-feature usage of permissions beyond stated scope # Zoom Phone and Avaya Phone System Integration Field Guide ### Overview In March 2024, Zoom announced a strategic partnership with Avaya in order to support customers who are running Avaya Aura (R10+) or Avaya Enterprise Cloud. This integration allows customers to have the Zoom Workplace application, while registering the Phone tab to Avaya. This document will help you understand the requirements, limitations, and Zoom integration process with Avaya hardware. #### Requirements This integration is supported on Windows, Mac, iOS and Android mobile devices, and VDI platforms running Zoom client version 6.3.10 or later. During the early phases of our partnership, we suggest that customers have the following: * Avaya Workplace with Session Initiation Protocol (SIP) support * Avaya Aura (R10+) or Avaya Enterprise Cloud * Avaya Aura Device Services (AADS), Session Manager (SM), and Remote Worker with Avaya Session Border Controller for Enterprise (ASBCE) deployed See the [Avaya Support Note](https://support.avaya.com/css/public/documents/101092003) for additional details. If your customer doesn’t meet all of these requirements, contact a pre-sales resource, Zoom account team member, or Avaya partner to discuss your options. #### Limitations The Phone tab in the Zoom Workplace application is a SIP softphone registered directly to Avaya. Since this setup doesn’t connect to Zoom Phone, there are a few limitations: * Zoom AI for Phone features. Since the audio doesn’t cross the Zoom cloud, we can’t provide any AI functions on live voice, recorded voice, or voicemail at this time. * Zoom Phone integrations aren’t supported. This includes Salesforce, ServiceNow, ZenDesk, and Microsoft Teams, among others. * Call Recording. All call recording is handled on the Avaya side. * Call Logs. All call logs are handled on the Avaya side. * Conference Calling. Conference calls are hosted on the Zoom Workplace application, with a limit of four total participants. The following items aren’t available: * Avaya Contact Center. We don’t support Avaya Contact Center agent-related features and functions with the phone system integration. * Avaya IP Office. This is a different private branch exchange (PBX) solution from Avaya. It isn’t included in this integration. * Bridged Appearances. This popular Avaya Communication Manager feature isn’t currently supported. See the [Avaya Support Note](https://support.avaya.com/css/public/documents/101092003) for additional limitations from the Avaya perspective. #### Architecture and Design {% hint style="warning" %} **Important**\ It **is** your responsibility to provide technical details about Zoom to customers, partners, or Avaya. It **is not** your responsibility to configure or help configure Avaya components. {% endhint %} The following chart shows a high-level representation of the integration between Zoom and Avaya. The integration between Zoom and Avaya hardware is straightforward to set up from the Zoom side, averaging between 10 and 30 minutes from start to finish. Your Avaya partner will have a more involved process, which you can [see here](https://support.avaya.com/css/public/documents/101092003).