MetaOffice Pro

We understand that our customers need to be confident using MetaOffice Pro, and be aware of our data collection practices.

Note

This section is subject to change and we recommend that you check back quarterly for updates.

Data Management Practices

Through the implementation of its different features, MetaOffice Pro access, processes and stores several kind of data:

• Office configuration
• Video/Audio configuration
• Users data

Here is how we're managing data for these different categories:

Data	Accessed	Cached	Stored	Notes
User profiles	✔	✔	✔	Accessed and updated after each login. Stored as long as the organization is active.
Office Configuration	✔	✔	✔	Accessed and updated after creation of a tab. Stored as long as the organization is active.
Video / Audio configuration	✔	✔	✔	Accessed at each connection Stored as long as the organization is active.
User data	✔	🚫	✔	Users data (AAD ID, UPN). Stored as long as the organization is active.
User presence	✔	🚫	🚫	Users presence. Accessed at each time the user connect to an office.
Teams channel	✔	🚫	🚫	Name and unique ID of the channel. No cache. Stored as long as the organization is active.
Teams conversations	🚫	🚫	🚫	No access. No cache. No storage.
Teams files	🚫	🚫	🚫	No access. No cache. No storage.

Microsoft Graph

Scope	Description	Justification	Admin Consent Required
User.Read	Retrieve the properties and relationships of user object.	Allows MetaOffice Pro to read user information and to display it in the UI.	No
OnlineMeetings.ReadWrite	Create Teams meetings.	Allows MetaOffice Pro to create a Teams meeting when a user meet an other one.	No
Presence.Read.All	Retrieve the presence of a user.	Allows MetaOffice Pro to read user presence and to display it in the UI.	No
Presence.ReadWrite	Retrieve and set the presence of a user.	Allows MetaOffice Pro to write the user presence.	No
Team.ReadBasic.All	Retrieve all Teams teams belongs to a user.	Allows MetaOffice Pro to read user teams and to display offices in the UI.	No
User.Read.All	Retrieve the properties and relationships of all user objects.	Allows MetaOffice Pro to read user information and to display it in the UI.	Yes
TeamsActivity.Send	Send an activity feed notification in the scope of a team	Allows MetaOffice to send a notification in the activity feed	No
TeamMember.Read.All	Get the conversationMember collection of a team	Allows MetaOffice to get the list of member in the team where the office tab is installed	Yes
email	Gives the app access to the user's primary email address in the form of the email claim		No
openid	Used to sign in with OpenID Connect
offline_access	Gives thee app access to resources on behalf of the user for an extended time.	When a user approves the offline_access scope, MetaOffice Pro can receive refresh tokens from the Microsoft identity platform token endpoint. Refresh tokens are long-lived. MetaOffice Pro can get new access tokens as older ones expire.	No
profile	Gives the app access to basic information about the user in the claims.		No

Azure communication services

Scope	Description	Justification	Admin Consent Required
Teams.ManageCalls	Manage calls in Teams.	Allows MetaOffice Pro Create Teams Meeting in behalf of the user	No
Teams.ManageChats	Manage chats in Teams.	Allows MetaOffice Pro to create group chat in behalf of the user.	No

TIP

The Azure AD App ID is: 64cc4cf9-18a6-4413-a175-1d144caa6cae

Architecture and flow diagram

Resource Endpoints

All the traffic from and to the TeamsPro platform uses HTTPS protocol on port 443. Here is a short description of each flow:

Name	Comments
metaoffice.teams-pro.com	for the apps including help contents
.msecnd.net and *.visualstudio.com	for performance metrics analysis

Dependencies