Streamline document-signing workflows and deliver amazing employee and customer experiences when you leverage Adobe Sign capabilities in Teams. You can sign documents, send them for legally binding e-signatures and approvals, and track their status, all with Adobe Sign for Teams, Microsoft's preferred e-sign solution.
What is the hosting environment or service model used to run your app?
Hybrid
Which hosting cloud providers does the app use?
Azure
Questions
Questions or updates to any of the information you see here? Contact us!
How the app handles data
This information has been provided by Adobe about how this app collects and stores organizational data and the control that your organization will have over the data the app collects.
Information
Response
Does the app or underlying infrastructure process any data relating to a Microsoft customer or their device?
Yes
What data is processed by your app?
Email and UserId. To sign user in to ensure their consent for the permission of using Adobe Sign app.
Does the app support TLS 1.1 or higher?
Yes
Does the app or underlying infrastructure store any Microsoft customer data?
Yes
What data is stored in your databases?
Transactional data (including original documents, workflow events, and final signed PDF documents) are securely stored within the data layer (databases and file store) managed by Adobe.
If underlying infastructure processes or stores Microsoft customer data, where is this data geographically stored?
United States of America
Do you have an established data rentention and disposal process?
Yes
How long is data retained after account termination?
Less than 30days
Do you have an established data access management process?
Yes
Do you transfer customer data or customer content to third parties or sub-processors?
Yes
Do you have data sharing agreements in place with any third party service you share Microsoft customer data with?
Yes
Questions
Questions or updates to any of the information you see here? Contact us!
Does the app perform automated decision making, including profiling that could have a legal effect or similar impact?
No
Does the app process customer data for a secondary purpose not described in the privacy notice (i.e. marketing, analytics)?
No
Do you process special categories of sensitive data (i.e. racial or ethnic origin, political opinion, religious or philosophical beliefs, genetic or biometric data, health data) or categories of data subject to breach notification laws?
Yes
Does the app collect or process data from minors (i.e., individuals under the age of 16)?
Yes
Is consent obtained from a parent or legal guardian?
Yes
Does the app have capabilities to delete an individual's personal data upon request?
Yes
Does the app have capabilities to restrict or limit the processing of an individual's personal data upon request?
Yes
Does the app provide individuals the ability to correct or update their personal data?
Yes
Are regular data security and privacy reviews performed (for example, Data Protection Impact Assessments or privacy risk assessments) to identify risks related to the processing of personal data for the app?
Yes
Questions
Questions or updates to any of the information you see here? Contact us!
Information
Response
Does your application integrate with Microsoft identity platform (Microsoft Entra ID) for single-sign on, API access, etc.?
Yes
Have you reviewed and complied with all applicable best practices outlined in the Microsoft identity platform integration checklist?
Yes
Does your app use the latest version of MSAL (Microsoft Authentication Library) or Microsoft Identity Web for authentication?
No
Does your app support Conditional Access policies?
No
If your app does not use one of the above libraries, what authentication library or libraries does it use?
Calls graph oauth endpoints directly
Does your app support Continuous Access Evaluation (CAE)
No
Does your app store any credentials in code?
No
Apps and add-ins for Microsoft 365 might use additional Microsoft APIs outside of Microsoft Graph. Does your app or add-in use additional Microsoft APIs?
Yes
Data access using Microsoft Graph
Graph Permission
Permission Type
Justification
Microsoft Entra App ID
Mail.ReadWrite
delegated
This permission is needed so that the app has the ability to open and download attachments in Outlook. With this ability, users can sign those attachments and send those attachments for signature within Outlook.
This permission is used when sending Agreements for signature in Outlook. It allows the app to perform type-ahead matching on the signers for that Agreement.
This permission is used to identify the Office user and get their email address so that the app can match the Office user with an Adobe Sign user. It is also used to verify that a users' access token is valid.
This permission is used so that actions can be taken on the user's behalf when they are not actively signed in to our add-in. In situations where the app only has access to an Identity Token (for example, Outlook) the app can securely identify the user and update the user's Access Token using the refresh token that the app gets from this permission. This is so that the user does not have to repeatedly sign in to Acrobat Sign each time they want to use the add-in.
This permission is used so that the app can acknowledge the log-in state for those users that logged into the Microsoft app (i.e. Teams, Outlook, etc.) with their work or school accounts. This permission also provides the app the ability to utilize the email and profile scopes.