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: August 17, 2021

General information

Information provided by Ambition to Microsoft:

Information Response
App name Ambition
ID WA200003159
Office 365 clients supported Microsoft Teams
Partner company name Ambition
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 Ambition 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
Channel.ReadBasic.All delegated Send Ambition Notifications to Channel Channel id & name. 24a9cf21-407c-41f9-8cc6-e7015f4e02af
Group.Read.All delegated Setup an Ambition Workflow notification to a particular Channel within a Team. Team's name & id. 24a9cf21-407c-41f9-8cc6-e7015f4e02af
User.Read delegated To identify the Admin who authorized the Ambition app Users name & email, to sync with Ambition users 24a9cf21-407c-41f9-8cc6-e7015f4e02af
User.ReadBasic.All delegated User's names & emails, to sync users with their Ambition accounts. User's names & emails are stored. 24a9cf21-407c-41f9-8cc6-e7015f4e02af
offline_access delegated To sync Microsoft Teams data while Users are offline. The OAuth Access Token & Refresh Token are stored. 24a9cf21-407c-41f9-8cc6-e7015f4e02af
openid delegated This is required to use Microsoft's sign-in feature N/A 24a9cf21-407c-41f9-8cc6-e7015f4e02af

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? Employee First Name, Last Name, Email Address Display/search/filter purposes

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?
Display purposes. Names & emails. To link Microsoft Users with their Ambition accounts.

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?

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.

Need-to-know access permissions.

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!

Identity information

This information has been provided by Ambition 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? Yes
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
For your app, what do you avoid using? - Wildcard redirect URIs,
- OAuth2 Implicit Flow, unless required for a SPA
- Resource Owner Password Credential (ROPC) flow
Does your app expose any web APIs? Yes
Does your permission model only allow calls to succeed if the client app receives the proper consent? Yes
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!