Announcement ID | MC816217 | Published Date | 07-17-2024 | |
Service | Copilot | Last Updated | 12-06-2024 | |
Category | Stay informed | Expiration Date | 04-28-2025 | |
Roadmap ID | 401124 | Action Required by Date | ||
Tags | Admin impact, New feature, User impact |
Summary |
---|
The message details the upcoming Scheduled prompts feature for Microsoft Copilot in Microsoft 365, which automates prompts at set times. It will be available in public preview in mid-December 2024 and general availability in mid-March 2025. Users need a Microsoft Copilot license, a Standard Microsoft Power Automate license, and the Optional Connected Experience admin toggle enabled. Admins can manage this feature through admin settings, and users can opt-in or out. Relevant data policies and privacy settings are also mentioned. |
More Information |
---|
Updated December 6, 2024: We have the timeline below. Please note that customers who are interested in joining the preview must opt-in. To join the preview, customers should file a support ticket requesting to join the Scheduled prompts preview. Thank you for your feedback. Coming soon for Microsoft Copilot for Microsoft 365: A new Scheduled prompts feature that allows users to automate Copilot prompts to run at set times and frequencies in Copilot in Microsoft Teams, Office.com/chat, and Microsoft Outlook for the web and Desktop. A Microsoft Copilot for Microsoft 365 license and a Standard Microsoft Power Automate license are required to use this feature. To be eligible, customers must also have the Optional Connected Experience (OCE) admin toggle enabled, and configure their DLP policies to allow the Copilot for Microsoft 365 connector in their default PowerPlatform environment. When this will happen:Public Preview: We will begin rolling out mid-December 2024 (previously mid-November) and expect to complete by late December 2024 (previously late November). General Availability: We will begin rolling out mid-March 2025 expect to complete by late March 2025 How this will affect your organization:Before this rollout: Users are unable to schedule Copilot for Microsoft 365 prompts to run at a specific time and frequency. After the rollout: Users can find the Scheduled prompts feature by hovering over a prompt they have submitted to Copilot or by clicking on the Schedule prompts button in the Copilot response footer (references images below). After configuring their Scheduled prompt, when a user selects the Save and activate button to confirm the scheduled prompt, a user's prompt information will be sent to the Power Automate and Power Platform system, and the Power Automate terms of service and privacy policy apply: Schedule prompt entry pointsSchedule prompt Creation dialogWhat you need to do to prepare:Managing the Scheduled prompts feature as an admin: To continue having the Scheduled prompts feature available in your organization, no action is required after completing the opt-in process. The feature is automatically included as part of the Optional Connected Experiences admin setting, which is on by default. Admins can access the Optional connected experiences setting at config.office.com If you prefer not to have this feature available to your organization, you can file a customer support ticket requesting to exit the preview program or disable the optional connected experiences setting at config.office.com. If you turn off the Optional connected experiences setting, this action will prevent anyone in your organization from seeing the Scheduled prompts feature in Copilot. If you choose to make these optional connected experiences available to your users, your users will also have the option to turn them by going to the privacy settings dialog box. To prevent exposing organizational data, you should also create a data policy in the Power Platform admin center. Creating a data policy in the center allows administrators to control access to these connectors in various ways to help reduce risk in your organization. If you disable this feature after someone in your organization has already used the feature:
Before rollout, we will update this post with revised documentation. |