# Calendar Pro

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


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, Calendar Pro access, processes and stores several kind of data:

  • Calendar events
  • Calendar 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.
Calendar Configuration Accessed and updated after creation of a tab.
Stored as long as the organization is active.
Calendar events 🚫 Accessed and updated of using the calendar.
Stored as long as the organization is active.
User data 🚫 Users data (AAD ID, UPN).
Stored as long as the organization is active.
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 Calendar Pro to read user information and to display it in the UI. No


The Azure AD App ID is: fb507a6d-2eaa-4f1f-b43a-140f388c4445

# Microsoft Teams Apps Security and Compliance

Microsoft works with our Microsoft 365 developer partners to provide the information organizations need to expedite and inform decisions about Microsoft Teams Apps and add-ins they use. The information is supplemented with information from the Microsoft Cloud App Security app catalog and information provided by the developers when they submit their applications. This security, data handling, and compliance information is intended to help organizations assess and manage risk in using these apps.

# Architecture and flow diagram

Calendar Pro architecture

# 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
calendar.teams-pro.com for the apps including help contents
.msecnd.net and *.visualstudio.com for performance metrics analysis

# Dependencies

# Client

# Server

Name Version Url License
Azure.Messaging.ServiceBus 7.2.0 https://licenses.nuget.org/MIT MIT
Microsoft.ApplicationInsights.AspNetCore 2.15.0 https://licenses.nuget.org/MIT MIT
Microsoft.AspNetCore.Mvc.NewtonsoftJson 3.1.14 https://licenses.nuget.org/Apache-2.0 Apache-2.0
Microsoft.AspNetCore.SpaServices.Extensions 3.1.9 https://licenses.nuget.org/Apache-2.0 Apache-2.0
Microsoft.Azure.DocumentDB 2.13.0 https://licenses.nuget.org/MIT MIT
Microsoft.Azure.DocumentDB.Core 2.13.0 https://licenses.nuget.org/MIT MIT
Microsoft.Extensions.HealthChecks 1.0.0 https://licenses.nuget.org/MIT MIT
Microsoft.Identity.Web 1.12.0 https://licenses.nuget.org/MIT MIT
Microsoft.Identity.Web.MicrosoftGraph 1.12.0 https://licenses.nuget.org/MIT MIT
Microsoft.Identity.Web.UI 1.4.1 https://licenses.nuget.org/MIT MIT
Newtonsoft.Json 13.0.1 https://licenses.nuget.org/MIT MIT
SendGrid 9.24.2 https://licenses.nuget.org/MIT MIT
Swashbuckle.AspNetCore.Swagger 5.6.3 https://raw.githubusercontent.com/domaindrivendev/Swashbuckle.AspNetCore/master/LICENSE MIT
Swashbuckle.AspNetCore.SwaggerGen 5.6.3 https://raw.githubusercontent.com/domaindrivendev/Swashbuckle.AspNetCore/master/LICENSE MIT
Swashbuckle.AspNetCore.SwaggerUI 5.6.3 https://raw.githubusercontent.com/domaindrivendev/Swashbuckle.AspNetCore/master/LICENSE MIT