Adobe Sign for SharePoint

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

General information

Information provided by Adobe Inc. to Microsoft:

Information Response
App name Adobe Sign for SharePoint
ID WA104381012
Office 365 clients supported SharePoint 2013 or later
Partner company name Adobe Inc.
URL of partner website https://acrobat.adobe.com/us/en/sign.html
URL of Privacy Policy https://www.adobe.com/privacy/policy.html
URL of Terms of Use https://www.adobe.com/legal/licenses-terms.html

Feedback

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 Inc. 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 To get user role and validating if user is granted certain permission for application feature. To refresh access token, when the current one is expired. 99a3ad8d-8682-4f2a-9c2c-b4b27e99585c

Data access using other Microsoft APIs

Apps and add-ins built on Microsoft 365 may use additional Microsoft APIs other than Microsoft Graph to collect or process organizational identifiable information (OII). List any Microsoft APIs other than Microsoft Graph this app uses.

API Is OII collected? What OII is Collected? Justification for collecting OII? Is OII stored? Justification for storing OII?
SharePoint REST API Yes SharePoint user roles Base on the user roles to grant/deny access to list items Not storing in DB Not Applicable

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.

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?

Our logs contain sufficient information to be able to identify and fix customer problems. Logs are retained for 90 days and access is restricted. Our database store hashed identification information for authentication while the user is offline. Database retention policy is 30 days from last used

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.

We do not have any customer admin interaction in our system for Microsoft Outlook application.

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?

Yes

Feedback

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

Identity information

This information has been provided by Adobe Inc. 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? No
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

Feedback

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