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 28, 2021

General information

Information provided by Aster to Microsoft:

Information Response
App name Aster
ID WA200002379
Office 365 clients supported Microsoft Teams
Partner company name Aster
URL of partner website
URL of Teams application info page
URL of Privacy Policy
URL of Terms of Use


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

How the app handles data

This information has been provided by Aster 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
Directory.Read.All delegated List of directories for sending Planner tasks of Sharepoint docs None 27c89ce8-b449-4959-b801-988d8b727512
Group.ReadWrite.All delegated List of groups for sending Planner tasks of Sharepoint docs in existing or created groups None 27c89ce8-b449-4959-b801-988d8b727512
Notes.ReadWrite.All delegated Notes contents for writing in OneNote None 27c89ce8-b449-4959-b801-988d8b727512
Tasks.ReadWrite.Shared delegated Tasks, assignation, deadlines All of this data for synchronizing Graph API tasks with Aster tasks 27c89ce8-b449-4959-b801-988d8b727512
User.Read delegated User email for identifying user User email in assignations for example 27c89ce8-b449-4959-b801-988d8b727512
offline_access delegated No data collected, just for seemlessly refresh the token None 27c89ce8-b449-4959-b801-988d8b727512

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.

Non-Microsoft services are not used.

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?
To communicate with the user in a human and personnalized way 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?

All accesses are logged, identified with users emails

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.

RGPD Contract

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?



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

Information from the Microsoft Cloud App Security catalog appears below.

View in a new tab


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

Identity information

This information has been provided by Aster 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? Yes
Does your app use MSAL (Microsoft Authentication Library) for authentication? No
Does your app support Conditional Access policies? No
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? No
Does your app support multi-tenancy? Yes
Does your app have a confidential client? Yes
Do you own all of the redirect Unified Resource Identifier (URI) registered for your app? Yes
Does your app expose any web APIs? No
Does your app use preview APIs? No
Does your app use deprecated APIs? No


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