The Microsoft 365 Delegated Access integration enables non-admin users to use Microsoft 365 steps in Torq workflows. When creating an instance of this integration you will be asked to give Torq limited permissions only to resources that your own Microsoft 365 user can access. Although limited, these permissions are sufficient for executing many of the most common use cases involving Microsoft 365.
You can use this integration in steps of the following Microsoft services:
Microsoft Excel
Microsoft OneDrive
Microsoft Outlook
Microsoft SharePoint
Create a Microsoft 365 Delegated Access Integration in Torq
If you're an admin, you will have the option to give Consent on behalf of your organization. If you choose this option, other users will still have to create their own integrations to have their own token to use in steps, but they won't have to accept the Torq app permission request.
If, when creating an instance of this integration, you're asked to get the approval of an admin, it's possible that your organization put restrictions to prevent users from adding any 3rd party applications to their accounts. You can ask your admin to check the Azure Active Directory (AAD) settings. This setting is required to create an instance of this integration without admin approval.
Go to Build > Integrations > Steps > Microsoft 365 Delegated Access, and click Add.
Type a meaningful name for the integration instance and click Add.
Click Accept.
How to Use
Create a Microsoft 365 Delegated Access integration in Torq.
Provide $.integrations.access_token as the access token in Microsoft Excel, OneDrive, Outlook, and Sharepoint steps.
Additional Information
These are the Microsoft 365 scopes requested by the Torq app:
offline_access
openid
emailprofile
User.Read
Files.ReadWrite.All
Mail.ReadWrite
Mail.Send
Calendars.ReadWrite
Contacts.ReadWrite
MailboxSettings.ReadWrite
Sites.ReadWrite.All