Collaboration controls

Warning

The Collaboration controls for model-driven applications are set to retire by May 2024. Retirement will be carried out in two phases to ensure a smooth transition. Following table details the timeline of the retirement process and its impacts:

Timeframe	Action	Impact
February 2024	Collaboration controls will no longer be available to install from AppSource.	- New deployments of the collaboration controls in Power Apps environments aren't possible. - Existing installations aren't affected.
May 2024	The internal service that powers the controls will be retired.	- The controls will stop supporting integration with Microsoft 365 and will return errors to users. Data generated and managed through the controls won't be impacted. For more information, see the table later in this article.

Artifacts created and managed through the controls will continue to exist after the service is retired.

Control	Impact
Approvals	Approvals created in the Approvals control will remain in the Approvals app but will no longer be accessible in the Approvals control.
Files	Files managed in the Files control will remain in SharePoint but will no longer be accessible in the Files control.
Meetings	Meetings created in the Meeting control will remain in Outlook and Teams calendars but will no longer be accessible in the Meetings control.
Notes	Notes created in the Notes control will remain in the Dataverse notes table.
Tasks	Tasks created in the Task control will remain in Planner but will no longer be accessible in the Task control.

We recommend removing the Collaboration controls and Collaboration connector from all Power Apps solutions and prepare users for the upcoming Collaboration controls retirement.

The Collaboration controls enable applying Microsoft 365 and Microsoft Teams for Approvals, Files, Meetings, Notes, and Tasks to enable contextual collaboration around business processes. These controls allow you to build custom collaborative experiences that can be surfaced right in Teams. The solutions that make up Collaboration controls allow makers to build applications that integrate with Microsoft 365 services like Planner, Bookings, Outlook, and SharePoint in a low code manner. Collaboration controls are available only in public developer preview.

These controls give you the power to simplify your users workflow collaboration by building custom apps for your org (LOB apps) and work without switching the context from app to app with the following:

• Approvals
• Files
• Meetings
• Notes
• Tasks

Following are some of the key capabilities of Collaboration controls:

• Microsoft Planner tasks: Create tasks and assign it to members of a record so that they can view a consolidated list of tasks in model driven app and tasks app in Microsoft Teams.

• Dataverse Tasks: Create tasks that can be assigned to users who are external to your organization.

• Dataverse Notes: Create notes that are assigned to a record in your app.

• Outlook Meetings: Schedule meetings with both customers and internal employees and seamlessly connect with others with Microsoft Teams with a select of a button.

• SharePoint Files: Share files with members of a record so that you can search, reference, and edit relevant artifacts in a centralized location backed by SharePoint.

• Approvals: Streamline requests within your team.

Note

By configuring and using the various Microsoft 365 capabilities of Collaboration controls mentioned earlier, you are granting permission for user data to pass through the Graph API and accepting Microsoft API terms of Use. For more information, see Microsoft Graph.

How Collaboration controls works

The controls run within a Power Apps Model Driven Application (MDA) that can be deployed to Microsoft Teams. MDA run on Microsoft Dataverse and can be integrated with a custom data model. The controls integrate with Microsoft Graph for Planner tasks, Outlook and Teams calendars, and SharePoint files. The Collaboration controls don't integrate directly with external sources, such as a system of record or a portal.

• Data can be added to Dataverse from external sources via standard OData APIs.

• Data can be read from Dataverse via standard OData APIs and submitted to external sources such as a system of record or a portal.

See also

• Integrate web apps
• Microsoft Graph overview