Deployment Requirements
Before deploying Meeting Insights, customers must provide the following:
| ■ | Customer’s domain name. |
| ■ | Email addresses of customer's contact points for the deployment status. |
| ■ | Microsoft Entra ID User Principal Names (UPNs) required for initial access (login) to Meeting Insights. |
| ● | You can use any user account for initial login. However, depending on your organization's Microsoft delegated permissions for applications policy (listed below), you may be prompted to request approval from your organization's administrator for consent to access the Meeting Insights application: |
| ✔ | Do not allow user consent: Consent is required from your organization's administrator. |
| ✔ | Allow user consent for apps from verified publishers, for selected permissions: User can consent (because Meeting Insights is a Microsoft-verified publisher). |
| ✔ | Allow user consent for apps: User can consent. |
| ● | During the onboarding process (see Connecting to Microsoft 365), multiple permissions (consents) for Microsoft 365 must be granted, which can only be done by users with Global Administrator or Cloud Application Administrator role, depending on consent type. These administrator users are used exclusively to grant the permissions; after each permission is granted, the Meeting Insights session automatically reverts to the user account who logged into Meeting Insights. |
| ■ | Preferable region for storing recordings. When a region is unavailable in Microsoft Azure Cloud, a default region is used. |