Skip to main content

Connect Outlook, Microsoft Teams and OneDrive with Eurekos - Article

Choose the Microsoft services your learning operation needs, configure their account dependencies and verify scheduling, content and attendance outcomes.
Updated: 14 Nov 2026
21 min read

Summary

Connect learning operations with the Microsoft tools your organization already uses. Outlook can carry training into everyday calendars, Teams can host live sessions and collaboration, and OneDrive can keep learning resources connected to maintained source documents.

These services share a platform connection but have different account, permission and verification requirements. A connected Microsoft identity alone does not enable every service or prove that a meeting was attended.

Use this article to:

  • Choose and configure the relevant Microsoft services
  • Distinguish service-account scheduling from user-connected features
  • Configure Teams attendance and verify the resulting learning evidence

Business Context

The Microsoft integration connects Eurekos with Microsoft 365 and Azure services, extending the platform beyond its native capabilities into a comprehensive enterprise ecosystem for scheduling, collaboration, and content management.

As Microsoft is a global provider of widely adopted productivity and infrastructure services, this integration represents far more than a simple feature extension. It enables a configurable set of capabilities across multiple functional areas, supporting both user experience and operational workflows in a cohesive and scalable way.

At its core, the integration supports three key domains:

  • Scheduling and coordination (Outlook Calendar)
  • Virtual delivery and collaboration (Microsoft Teams)
  • Content and document management (OneDrive)

This makes the integration particularly valuable for organizations that:

  • Deliver instructor-led, virtual or blended learning
  • Use Microsoft 365 as part of their ecosystem
  • Require alignment between learning activities and operational tools

The objective of this integration is to streamline and centralize your existing enterprise ecosystem for both administrators and learners by leveraging familiar Microsoft tools. It enables organizations to make use of existing files, data, and workflows while improving user experience, reducing manual effort, and minimizing the risk of human error.

At the same time, it introduces a higher level of automation and operational efficiency—particularly in scheduling and delivery—by ensuring that processes are handled consistently across systems. For example:

  • Events are created once in Eurekos
  • Invitations, meeting links, and updates are handled automatically
  • The supported changes are reflected through each service’s specific synchronization behavior

This integration offers multiple configuration options, allowing each organization to decide which capabilities to enable based on its specific needs. It supports a granular approach to feature activation, including precise control over permissions and security settings—both of which are critical in enterprise environments.

These requirements often vary significantly between organizations and may also differ across user groups, particularly when supporting external audiences. This flexibility ensures that the integration can be aligned with both internal governance policies and diverse user scenarios.

Feature Overview

The Microsoft integration enables multiple services within Eurekos, each with a distinct purpose but shared configuration.

ServiceFunction
Outlook CalendarSends and synchronizes supported event invitations through the configured service account for users whose profile enables Outlook synchronization
Microsoft TeamsEnables creation of virtual meeting links and collaboration  enrollment capability from specific teams
OneDriveAllows access to files within course content and optionally the ability to collaborate on Office 365 using Microsoft Online

These services are activated centrally by administrators but may require user-level connection to function fully, depending on the specific use case and implementation. This dependency is explained in detail within each section below, where relevant.

How the Integration Works

The Microsoft integration in Eurekos is built around a layered model that separates configuration, execution, and user interaction, allowing organizations to combine centralized control with flexible user-level functionality.

1. Platform Configuration (Administrator) → Administrators define the integration by configuring:

  • A Microsoft Azure application
  • Required Microsoft Graph API permissions (e.g. Teams, OneDrive, Outlook)
  • Defining which services are enabled in Eurekos

This layer determines what capabilities are available, such as creating Teams meetings, accessing OneDrive files, or sending Outlook invitations. 

2. System Execution (Service Account & Microsoft APIs) → Once configured, Eurekos communicates with Microsoft through Microsoft Graph APIs.

  • A service account is used for scheduling and sending calendar invitations
  • This account behaves like a real user sending invites, ensuring proper Outlook RSVP functionality
  • File access are handled through Microsoft services

This enables key operational use cases such as:

  • Creating events once in Eurekos and distributing them as Outlook invitations
  • Automatically generating Teams meeting links for virtual sessions
  • Checking the supported updates in each service

3. User Interaction (Where Required) → Some features depend on user-level interaction:

  • Users may connect their Microsoft account (required for Teams and OneDrive)
  • Users may enable or disable calendar synchronization in their profile

This layer ensures:

  • Controlled data sharing and user consent
  • Flexibility for mixed audiences (internal vs external)
  • Alignment with governance and privacy requirements
Microsoft Entra application permissions support separate Eurekos workflows. Outlook uses a service account and recipient calendar-sync preferences; Teams uses a connected organizer; OneDrive uses a connected author. Microsoft SSO remains separate.
Configure each Microsoft service for its own purpose: Outlook calendar synchronization, Teams delivery and attendance, or access to OneDrive source files.

Below you will find detailed guidance on the available configuration options for the Microsoft integration, including how each setting impacts functionality and behavior within Eurekos.

Outlook Calendar and synchronization

The Outlook service account sends supported Eurekos events as Outlook invitations for users whose profiles enable Sync events with Outlook calendar. The recipient does not need to connect a personal Microsoft account in Connected accounts for this route. Using Microsoft SSO does not, on its own, enable Outlook synchronization.

This matters for mixed customer, partner and internal audiences: separate the organization’s service account from the learner’s invitation preference and from the personal Microsoft connections used by meeting creators and OneDrive authors.

ConditionConsequence
Outlook enabled and service account connectedProvides the platform route for supported calendar invitations
User profile synchronization enabledIncludes that person in the applicable synchronization route
User profile synchronization disabledDoes not include that person in that automatic route
Personal Microsoft account connectedSupports the relevant user-connected services; does not replace the Outlook profile setting

Synchronization covers related future events and existing events whose End date is within the previous 24 hours. Newly created events and supported changes to existing events are processed in the background. Relevant items can include Calendar and Community events, Event modules, scheduled Course modules and scheduled learning paths, depending on platform configuration. In particular, treating an Activity itself as a calendar item is a separate configuration choice.

The invitation carries the event’s title, schedule and time zone, description, location and webinar link where provided. Supported changes send updated calendar information. Cancellation of a connected Calendar event or Event module removes the corresponding Outlook item. Verify the representative Event and Activity routes used by your organization.

A restricted Event module can synchronize even while its learning access is restricted. An unseen adaptive Event module is not synchronized until it becomes available. Review this distinction before assuming that a learning restriction also hides a date from someone’s calendar.

Coordinate invitation and platform communication

Outlook invitations and Eurekos System Email are separate communication routes. Review both to avoid duplicate messages. Accepting or declining an Outlook invitation, or deleting a personal calendar item, does not itself change the learner’s Eurekos enrollment or prove attendance.

A one-time Add to Calendar file is also different from automatic synchronization. It lets the recipient import an event into a calendar; it should not be used as evidence that the Microsoft service-account route is connected. Use the System Email Notification Overview to investigate platform emails separately.

Microsoft Teams

Microsoft Teams integration enables virtual session delivery by allowing Eurekos to generate Teams meeting links directly during event creation, significantly reducing manual effort and avoiding duplication across systems.

Beyond meeting creation, this integration introduces a collaboration layer that extends the learning experience into Microsoft Teams. Activities in Eurekos can be connected to existing Teams, allowing organizations to align training delivery with established communication, file sharing, and collaboration workflows.

This is particularly valuable for organizations already using Microsoft Teams extensively, as it enables learning activities to take place within familiar tools while maintaining a centralized experience in Eurekos. At the same time, it supports governance and privacy requirements by leveraging Microsoft’s existing permission structures.

Activity Connection and User Synchronization

Microsoft Teams integration operates directly at the activity level, where administrators define how collaboration and participant management should be handled for each training activity.

When configuring an activity, administrators can connect an existing Microsoft Team. This establishes a relationship between the activity and the collaboration space in Teams, enabling structured interaction around the learning experience.

From a workflow perspective, this supports two key use cases:

  • Collaboration space → Participants enrolled in the activity can be added to the connected Microsoft Team, giving them access to communication, shared files, and ongoing interaction related to the training
  • Enrollment source → Administrators can use an existing Microsoft Team as the basis for enrollment, adding its members directly into the activity and reducing manual user management

Synchronization behavior

Synchronization between Eurekos and Microsoft Teams is event-driven and controlled from Eurekos, rather than continuously synchronized between systems.

  • Enrolling users into an activity → may add them to the connected Microsoft Team
  • Using a Team for enrollment → adds Team members into the activity
  • Changes made directly in Microsoft Teams → are not automatically reflected back in Eurekos

This ensures that Eurekos remains the system of control for training participation, while Microsoft Teams serves as the collaboration layer.

Key Use Cases

  • Automatic meeting link creation → When scheduling events, users with a connected Microsoft account can automatically generate Microsoft Teams meeting links. These are embedded directly into the event workflow, ensuring consistency and eliminating the risk of incorrect or manually copied links
  • Collaboration in Microsoft Teams → Administrators can connect a Microsoft Team to an activity, allowing participants to collaborate in a shared space. The Team is accessible from within Eurekos, enabling a seamless transition between learning and collaboration
  • Enrollment via Teams → Existing Microsoft Teams can be used as a source for enrollment, allowing administrators to add groups of users efficiently without duplicating user management efforts

Important Considerations

  • Available Teams are determined by Microsoft permissions and access control, outside of Eurekos
  • Users must have a connected Microsoft account to create meetings or interact with Teams functionality
  • Organizational policies in Microsoft (e.g. group visibility, external access) directly impact what can be configured

⚠️ This integration follows Microsoft’s security and consent model. Eurekos does not control which Teams are visible or accessible beyond the permissions granted in Azure.

Explore the relevant articles for detailed guidance on how to use and configure these features in practice.

Configure automatic Teams attendance

Use automatic attendance when you need evidence of time present in a scheduled Teams session. Creating a meeting link or clicking Join does not establish that the learner attended for the required duration.

Configuration layerRequired choice or dependency
Microsoft applicationApprove the supported Graph permission set, including OnlineMeetingArtifact.Read.All for attendance reports
Platform Teams serviceEnable Teams and Enable automatic attendance marking
Meeting creatorConnect or reconnect their Microsoft account so the organizer can retrieve the meeting report
Event or Event moduleEnable Mark attendance automatically and review Required attendance time

Platform default and the requirement for one Event

The platform-wide default for Required attendance time is 70%. This default is managed by Eurekos and is not an ordinary administrator setting. Contact Eurekos support if your organization needs the platform-wide default changed.

The Event form has a separate Required attendance time field when Mark attendance automatically is enabled. It is prefilled from the default and accepts whole percentages from 1 to 100. An authorized Event editor can set the requirement for that Event without changing the platform-wide default.

For example, with the default 70% requirement, a participant needs at least 42 minutes within the scheduled period of a 60-minute Event. Forty minutes does not meet that requirement. Time outside the scheduled Eurekos period does not increase the qualifying percentage.

How attendance maps to the Event status

After the scheduled end, Eurekos retrieves the report when Microsoft makes it available, combines the supported join/leave intervals within the scheduled period and matches the reported email addresses to Eurekos participants.

Existing attendanceReport evidenceResult
Not markedMatched participant meets or exceeds the Event requirementAttended
Not markedMatched participant is below the Event requirementNot attended
Not markedParticipant is absent from the returned reportNot marked
Already marked AttendedAny returned attendance evidenceKeeps Attended
Already marked Not attendedMatched participant meets the requirementChanges to Attended; otherwise keeps Not attended

These are attendance outcomes. Event or Activity completion, practical assessment and certificate issuance still follow their own configured criteria. Time present is not evidence that a learner understood the material or completed a practical task.

Rollout and later changes

Enabling the platform capability does not automatically enable marking on existing Activities or Events. Review each intended Event. An existing meeting creator may need to reconnect Microsoft after the attendance permissions are added.

Participants do not need to connect Microsoft in their Eurekos profiles just for attendance matching. Microsoft must return an email address that matches the participant’s Eurekos account, and the original organizer’s account must remain connected. Attendance is obtained from the organizer’s meeting report, not from each participant’s mailbox; an on-premises mailbox alone therefore does not decide whether Teams attendance can be matched.

Check organizer-as-participant and restarted-meeting scenarios before relying on them for certification. Disconnecting or deleting the organizer, removing the conference or disabling attendance can stop the applicable retrieval route. Once a report has been processed, changing the required percentage alone does not recalculate the stored attendance.

OneDrive

OneDrive integration enables content creators to use externally managed files directly within Eurekos course content. For many organizations, it is preferable to maintain documents centrally in OneDrive—ensuring they are always up to date—while exposing them seamlessly within courses using Eurekos’ native authoring capabilities.

This allows administrators and content creators to reference live documents rather than uploading static files. Depending on how the content is shared in Microsoft, files can be made available either to anyone with access to the link or restricted to authorized users, in line with organizational governance and permission settings.

Collaborative Editing and File Management

In addition to content display, OneDrive integration also supports collaborative editing workflows for users with connected Microsoft accounts.

A key use case is within Eurekos Communities, where Office documents (such as Word or Excel files) are shared within native archives. Instead of downloading, editing, and re-uploading files with each change, users can open and edit documents directly in Microsoft Online via their browser. Changes are automatically saved back into the native archives, ensuring that the most recent version is always available.

From a user perspective, this creates a seamless editing experience, while technically the file is temporarily handled within the user’s OneDrive during the editing session—following Microsoft’s standard co-authoring model. This enables efficient collaboration without requiring users to leave the Eurekos environment or manage multiple file versions manually.

The OneDrive integration supports two key use cases:

  • Content authoring → Course authors can create dynamic content by linking to a OneDrive folder and presenting an automatically updated list of files within a course page. This ensures that the linked source remains maintained in OneDrive, eliminating the need to manually re-upload content into course pages with changes or additions to the contents of the folder in OneDrive
  • Co-authoring and collaborative editing → Users—such as community members or administrators working in the file archive of Eurekos—can edit Office documents directly in the browser using Microsoft Online. Changes are saved automatically, enabling real-time collaboration without version conflicts or repeated downloads and uploads

It is important to note that this functionality depends on Microsoft permission settings and organizational governance policies. In some environments, IT restrictions may limit who has access to which folders. Each user must connect their account in the profile.

Once OneDrive has been configured, users interacting with relevant features—such as Community members accessing a team or administrators managing files within the file archive—will be prompted to connect their Microsoft account. This ensures they are aware of and able to use the available integration features, such as accessing and editing files directly through Microsoft services.

For more detailed guidance on how to use these features, refer to the relevant articles.

The Course file-selection connection uses the author’s personal OneDrive, not an arbitrary shared SharePoint library. The author must use a genuine sign-in rather than Masquerade. Files link access permissions determines whether the generated link permits anyone with the link or only people signed into the organization. Choose that deliberately for external customer and partner audiences.

Configuration

To connect Eurekos with Microsoft services, you must create and configure an application in Microsoft Azure.

Step 1: Create Azure Application

Go to https://portal.azure.com → Microsoft Entra ID → App registrations, and create a New registration.

In the Register an application form:

  • Enter a name for the application
  • Select the appropriate Supported account type based on your organization’s needs
  • Provide the Redirect URL, which can be found in Settings → Third party integrations → Microsoft in your Eurekos platform

Ensure the Redirect URL is entered exactly as shown to allow proper authentication flow.

⚠️ Ensure that “Web” is selected as the application type, and enter the provided Redirect URL in the Redirect URI field when registering the application in Microsoft Entra ID. Refer to the Microsoft documentation and recommendations for tenant and account types.

Step 2: Agree the service permissions

In the registered application, open API permissions → Add a permission → Microsoft Graph → Delegated permissions. The reference below preserves the exact permission names used by the supported service configuration, so your Microsoft tenant administrator can assess the requested operations and grant the appropriate consent.

The current Teams connection requests a shared permission set covering user, group, Team and meeting operations. It is not an attendance-only permission profile. Removing a permission because one individual meeting workflow appears not to use it can break the connection. Outlook and OneDrive requirements also depend on whether those services are enabled.

The permission purpose and the actual Eurekos process are different scopes: Eurekos retrieves attendance reports for meetings connected to Eurekos Events, while a granted Microsoft permission can authorize broader operations. Use the Microsoft Graph permissions reference with the service configuration when reviewing consent.

Step 3: Configure the permissions for each enabled service

Use these groups to understand the configuration and troubleshoot a missing capability. They explain the permission purpose; they are not instructions to reduce the current shared Teams permission set to an unsupported subset.

OneDrive file access and editing

Delegated permissionPurpose
Files.ReadRead the signed-in user’s permitted files for the supported file-selection workflow
Files.ReadWriteRead and write the signed-in user’s permitted files for supported online editing

Connect Teams and synchronize members

The Team connection and supported enrollment/membership actions use Team and user permissions in addition to the meeting permissions.

Delegated permissionPurpose
Team.ReadBasic.AllRead available Team names and basic information
TeamMember.Read.AllRead Team membership
TeamMember.ReadWrite.AllManage the supported Team membership operations
User.Read.AllRead user profiles used by the supported synchronization
User.ReadBasic.AllRead basic user profile information
User.Invite.AllInvite users where the supported membership flow requires it

Directory and group operations

The shared configuration can also include directory and group access. Review these rights explicitly with the tenant administrator rather than confusing group membership with a single Teams meeting.

Delegated permissionPurpose
Directory.Read.AllRead directory information
Directory.ReadWrite.AllRead and write directory data within the granted delegated access
Group.Read.AllRead group information
Group.ReadWrite.AllRead and write group information
GroupMember.Read.AllRead group membership
GroupMember.ReadWrite.AllRead and write group membership

Teams meetings and attendance reports

Creating a meeting and retrieving its attendance report require different permissions.

Delegated permissionPurpose
OnlineMeetings.ReadRead online meeting information
OnlineMeetings.ReadWriteCreate and manage online meetings
OnlineMeetingArtifact.Read.AllRead meeting artifacts used to obtain attendance reports

The Outlook calendar permissions remain listed with the service-account procedure below. Permission approval does not replace the user’s connection, the enabled platform service or the Event’s automatic-attendance settings.

Step 4: Grant Administrator Consents

After adding the required API permissions, you must grant admin consent for these permissions.

This action requires administrator privileges in Microsoft Azure. By granting admin consent, the administrator approves the data exchange between Eurekos and Microsoft services on behalf of the entire organization.

Users may still need to connect or reconnect their accounts when the enabled services or approved permissions change. Administrator consent and a user’s actual connection are different steps.

Step 5: Generate Client Secret

Generate a new Client Secret in the Azure Portal under Certificates & secrets.

Once created, copy the secret value and navigate to Settings → Third party integrations → Microsoft in Eurekos, where you must provide:

Eurekos fieldWhat to provide
Application account typeThe intended Singletenant or Multitenant account configuration
Tenant ID, where shownThe directory identifier required by the selected tenant configuration
Application (client) IDThe identifier from the registered application’s Overview
SecretThe client secret value generated for that application
Redirect URLUse the exact URL displayed by Eurekos when registering the application callback

Ensure the secret is copied and stored securely, as it may not be fully visible again after creation.

Microsoft integration configuration screen in Eurekos, where administrators define application account type, tenant ID, client ID, secret, and redirect URL for Azure connection.
Microsoft integration configuration screen in Eurekos, where administrators define application account type, tenant ID, client ID, secret, and redirect URL for Azure connection.

Connect the people who use account-based features

Meeting creators and OneDrive authors open their profile’s Connected accounts tab and connect Microsoft using the intended account. Reconnect when permissions or the account authorization need refreshing. A learner who only receives service-account Outlook invitations does not need this personal connection.

Edit profile on the Connected accounts tab, with Microsoft shown as connected through the Disconnect action
Connect a personal Microsoft account for the relevant Teams and OneDrive features. Outlook recipients use their separate profile synchronization setting.

Step 6: Configure Service Account (Outlook Synchronization)

The Service Account is a standard Microsoft account with access to Outlook, used by Eurekos to send calendar invitations and manage event synchronization on behalf of the organization.

It effectively replicates a manual invitation workflow—ensuring that users receive proper Outlook meeting invitations with RSVP functionality—but does so automatically and at scale. This introduces several operational advantages, including consistent delivery, reduced manual effort, and centralized scheduling.

To enable this functionality, both additional API permissions in Azure and configuration in Eurekos are required.

6.1 Add Required API Permissions (Outlook)

Navigate to API permissions → Add permission → Microsoft Graph → Delegated permissions. Add the following permissions:

PermissionDescription
Calendars.ReadAllows reading calendar events for synchronization
Calendars.ReadBasicProvides basic calendar access
Calendars.Read.SharedEnables access to shared calendars
Calendars.ReadWriteAllows creating and updating calendar events
Calendars.ReadWrite.SharedEnables managing events in shared calendars

These permissions enable Eurekos to create, update, and synchronize Outlook calendar events, including sending RSVP-enabled invitations to users.

6.2 Add Service Account Redirect URL

In your Azure application, go to Authentication and add the following Redirect URI: https://yourdomain/mtx/microsoft/service-account/connect. This endpoint is required for authenticating the service account used for calendar management.

6.3 Connect Service Account in Eurekos

Navigate to Settings → Third party integrations → Microsoft.

Once the application credentials are correctly configured, the option to connect a Service Account becomes available.

  • Click [Connect]
  • Authenticate using the Microsoft account that will act as the service account

6.4 Administrative Actions (Post-Setup)

After successful authentication, a set of administrative helper actions becomes available. These are designed to support rollout, onboarding, and ongoing management of Outlook synchronization.

ActionDescriptionImpact
Enable Outlook sync by defaultAutomatically enables calendar synchronization for all newly created users by setting the “Sync events with Outlook calendar” option on their profileEnsures frictionless onboarding and immediate inclusion in scheduling workflows
Opt-in all usersActivates calendar synchronization for all existing users, allowing them to receive Outlook invitationsBrings current users into the scheduling flow without affecting past events
Sync outlook calendarInitiates background synchronization for opted-in users, covering related future events and past events whose End date is within the previous 24 hoursProcesses the eligible calendar set; does not import the complete historical calendar
Calendar availability statusDefines how events appear in recipients’ Outlook calendars (Free, Busy, Tentative, Working elsewhere, Unknown)Controls how event time is represented and whether it blocks availability in user calendars

Calendar Availability Behavior

The selected availability status determines how events are displayed in Outlook:

  • Free → Event appears immediately as free time
  • All other statuses → Event may initially appear as Tentative until accepted
  • Once accepted, the selected status is applied

Important considerations:

  • Applies only to newly created events
  • Existing calendar invitations are not updated
  • Final behavior may vary depending on Outlook or other calendar clients, as interpretation is handled outside Eurekos

These actions provide administrators with control over how synchronization is introduced—whether gradually or across the entire user base.

💡 Users retain control at all times and can opt out of calendar synchronization directly from their profile. This ensures alignment with user preferences and supports good governance practices related to notifications and data sharing.

Verify the connected workflows

Test the enabled services with the people who will operate them and the audiences who will consume them. Keep the background synchronization and provider report delay in mind.

Scenario or checkExpected result or evidence
Outlook recipient without Connected accounts linkWith profile opt-in and the service route configured, the intended invitation is delivered
Outlook profile opt-outThe intended future synchronization behavior respects the user’s profile setting
Invitation acceptanceCalendar availability behaves as configured; enrollment and attendance remain separate
Teams creator accountThe intended connected creator generates the meeting link
Teams enrollment and collaborationThe Activity/Team relationship adds the intended people without assuming every provider-side membership change returns to Eurekos
Teams attendance thresholdAfter the provider report is available, matched participant emails and scheduled participation produce the expected Attendees status
Teams schedule or title changedCheck the provider meeting as well; Eurekos Event changes are not universally mirrored to the Teams meeting
Later threshold changePreviously processed attendance is reviewed rather than assumed to recalculate
OneDrive course contentThe author can select the intended personal folder and a representative external learner has the intended access
Office document editingA permitted edit reaches the source/archive through the supported online-editing workflow
Account or service changeReconnection and the effect on existing meetings are checked before rollout

Maintain the connection

Roll out the services your organization needs, rather than enabling every option at once. Keep service-account ownership, secret renewal, account reconnection and a small representative test group in your maintenance plan. Recheck customer and partner access when changing OneDrive link permissions or Microsoft tenant policy.

Troubleshooting

ProblemWhat to check
Outlook invitation is missingOutlook enabled, service account connection, user profile opt-in and synchronization processing; a personal connected account is not required for this route
Teams link is not generatedThe meeting creator’s connected Microsoft account and approved service permissions
Teams attendance remains unmarkedScheduled end, report availability, matching email addresses, organizer connection and both platform/Event attendance settings
Meeting details differ in TeamsProvider-side update limitations; do not assume all Eurekos edits are mirrored
Changed attendance percentage has no effectWhether the report was already processed; later threshold changes do not automatically recalculate it
External learner cannot use OneDrive contentGenerated link access, tenant sharing policy and source permissions
Shared SharePoint folder is unavailable in the pickerThe connection selects from the author’s personal OneDrive

Third Party Integrations

FAQ