POPP Cloud VoIP Connector

Publisher Attestation: The information on this page is based on a self-assessment report provided by the app developer on the security, compliance, and data handling practices followed by this app. Microsoft makes no guarantees regarding the accuracy of the information.

Last updated by the developer on: September 20, 2021

General information

Information provided by POPP Communications to Microsoft:

Information Response
App name POPP Cloud VoIP Connector
ID WA200003306
Office 365 clients supported Microsoft Teams
Partner company name POPP Communications
URL of partner website https://popp.com
URL of Privacy Policy https://popp.com/terms/privacy-policy/
URL of Terms of Use https://popp.com/pvnterms/

Feedback

Questions or updates to any of the information you see here? Contact us!

How the app handles data

This information has been provided by POPP Communications about how this app collects and stores organizational data and the control that your organization will have over the data the app collects.

Data access using Microsoft Graph

List any Microsoft Graph permissions this app requires.

Permission Type of permission (Delegated/ Application) Is data collected? Justification for collecting it? Is data stored? Justification for storing it? Azure AD App ID
ChannelMember.Read.All delegated User IDs and display names of members of the current channel. The app uses this to present the user with a list of channel members to call. Metaswitch does not store this data. b8e57f6b-31cf-468e-9e99-81f0395cb1f9
Chat.Read delegated What data is collected or used? Add justification for collecting or using the data. User IDs and display names of members of the current chat. The app uses this to present the user with a list of chat members to call. Metaswitch does not store this data. b8e57f6b-31cf-468e-9e99-81f0395cb1f9
TeamMember.Read.All delegated User IDs and display names of members of the current team. The app uses this to present the user with a list of team members to call. Metaswitch does not store this data. b8e57f6b-31cf-468e-9e99-81f0395cb1f9
User.Read.All delegated What data is collected or used? Add justification for collecting or using the data. The business and mobile phone numbers of users. This is required so that phone calls to these numbers can be initiated. Metaswitch does not store this data b8e57f6b-31cf-468e-9e99-81f0395cb1f9
openid delegated An authorization token for the user, authorizing the app to access the other Graph API endpoints listed on their behalf. Metaswitch does not store this data. b8e57f6b-31cf-468e-9e99-81f0395cb1f9

Data access using other Microsoft APIs

Apps and add-ins built on Microsoft 365 may use additional Microsoft APIs other than Microsoft Graph to collect or process organizational identifiable information (OII). List any Microsoft APIs other than Microsoft Graph this app uses.

API Is OII collected? What OII is Collected? Justification for collecting OII? Is OII stored? Justification for storing OII?
Microsoft Identity Platform No

Non-Microsoft services used

If the app transfers or shares organizational data with non-Microsoft service, list the non-Microsoft service the app uses, what data is transferred, and include a justification for why the app needs to transfer this information.

All non-Microsoft services OII is transferred to What OII is transferred? Justification for transferring OII?
Metaswitch Networks and POPP Communications The following OII is transferred to the MCT Hosted Bot Server: Azure AD tenant ID Team IDs Channel/Chat IDs Message contents are also be transferred, which could potentially include OII The following OII may be transferred to the CommPortal JSON API: Phone numbers of users in a Business Group The domains of email addresses User IP addresses Add justification for why you need to transfer OII The app’s primary purpose is to facilitate telephone calls. If a user attempts to make a telephone call, this information must be provided to log in to their CommPortal account and correlate the call back to the correct user. The OII which is transferred to the MCT Hosted Bot Server is built into the Bot Framework API which is used to integrate with Teams and cannot be avoided.

Data access via bots

If this app contains a bot or a messaging extension, it can access end-user identifiable information (EUII): the roster (first name, last name, display name, email address) of any team member in a team or chat it's added to. Does this app make use of this capability?

Justification for accessing EUII? Is EUII stored in database(s)? Justification for storing EUII?
The app’s primary purpose is to facilitate telephone calls. If a user attempts to make a telephone call, EUII for all parties in the call must be provided to establish the call between the correct telephony users. No

Telemetry data

Does any organizational identifiable information (OII) or end-user identifiable information (EUII) appear in this application's telemetry or logs? If yes, describe what data is stored and what are the retention and removal policies?

No OII or EUII appear in the applications telemetry or logs.

Organizational controls for data stored by partner

Describe how organization's administrators can control their information in partner systems? e.g. deletion, retention, auditing, archiving, end-user policy, etc.

Metaswitch and POPP does not store the data for longer than the immediate need to load the MCT web pages from CommPortal Web. The data is not retained, and is immediately removed.

Human review of organizational information

Are humans involved in reviewing or analyzing any organizational identifiable information (OII) data that is collected or stored by this app?

No

Feedback

Questions or updates to any of the information you see here? Contact us!

Identity information

This information has been provided by POPP Communications about how this app handles authentication, authorization, application registration best practices, and other Identity criteria.

Information Response
Do you integrate with Microsoft Identify Platform (Azure AD)? Yes
Have you reviewed and complied with all applicable best practices outlined in the Microsoft identity platform integration checklist? No
Does your app use MSAL (Microsoft Authentication Library) for authentication? Yes
Does your app support Conditional Access policies? Yes
List the types of policies supported Conditional Access policies to the extent that such support is provided automatically by the MSAL library used for authentication.
Does your app request least privilege permissions for your scenario? Yes
Does your app's statically registered permissions accurately reflect the permissions your app will request dynamically and incrementally? Yes
Does your app support multi-tenancy? No
Does your app have a confidential client? No
Do you own all of the redirect Unified Resource Identifier (URI) registered for your app? Yes
For your app, what do you avoid using? - Wildcard redirect URIs,

Does your app expose any web APIs? No
Does your app use preview APIs? No
Does your app use deprecated APIs? No

Feedback

Questions or updates to any of the information you see here? Contact us!