Not all Microsoft Copilot features follow the same access rules. An app may be visible but require a licence to produce a result, while a feature marked Frontier remains in preview. Here’s how to choose which uses to test and check their implications for your organisation’s data.
Meeting Recaps in Teams: the app alone is not enough
The Meeting Recaps app brings Teams meeting recaps together in one place. It saves you from searching separately for the notes and follow-up tasks associated with each meeting. But its presence in Teams does not mean every user can view every type of recap.
The Microsoft Learn documentation on Meeting Recaps distinguishes access to the app from the licences required for its content:
| Feature | Requirement specified by Microsoft | Practical implication |
|---|---|---|
| Open Meeting Recaps | Available to all users | The app’s presence does not guarantee an intelligent recap |
| Intelligent text recap | Teams Premium or a Microsoft Copilot licence | Check the user’s licence before the pilot |
| Video or audio recap | Microsoft Copilot licence | Do not assume a Teams Premium licence alone provides access |
Another limitation to bear in mind: Meeting Recaps only shows meetings recorded or transcribed in the last 30 days. Microsoft lists support in Teams for Windows, Mac and the web; mobile support is still described as coming soon. If a meeting is missing, first check whether it was recorded or transcribed, its date and the relevant licence rather than assuming there is an outage.
Copilot sharing: choose what the recipient receives
Sharing a response and sharing a conversation serve different purposes. According to the Microsoft Learn documentation on Microsoft Copilot sharing, a shared response also includes the prompt that produced it. A shared conversation sends a snapshot: if the recipient continues it, Copilot creates a separate copy in their own history.
| Option | What is shared | Suitable use |
|---|---|---|
| Share a response | The response and its prompt | Show a specific result and how it was requested |
| Share a conversation | A copy of the conversation at the time of sharing | Let a colleague pursue a line of inquiry independently |
The link does not change permissions for Microsoft 365 files, emails or meetings mentioned in the exchange. It can, however, expose text already included in the shared snapshot. Review prompts and responses before distributing the link. Microsoft notes that administrators can disable this sharing, which is enabled by default; this setting is worth reviewing if your teams handle sensitive data.
A shared link does not grant access to documents
The recipient can read the content shared by Copilot without gaining access to the Microsoft 365 resources it mentions. Check permissions on those resources and the confidentiality of the shared text separately.
For a team preparing several proposals, sharing a conversation can provide a common starting point. Each colleague then continues their own copy; their new messages do not become part of a shared conversation. If you only need to standardise an instruction, it is better to distribute a reviewed prompt, as described in our guide to saving your Copilot prompts.
The Try again button serves a different purpose: rerunning a prompt after selecting another model. It is useful for comparing the structure and accuracy of two responses, without assuming one model will always be better. If you need to retain the first version, copy it before trying again: the example shown does not guarantee that you can return to the previous response.
Copilot Notebooks: check access before sharing a project
Copilot Notebooks brings references and exchanges about a subject together. A notebook for a sales proposal, for example, can collect the working documents and conversations needed to prepare it. The interface in Microsoft Copilot is designed for lightweight access; opening the notebook in OneNote offers other ways to work. This does not mean there are two independent copies of the project.
Requirements vary by tool. The Microsoft Learn documentation on Copilot Notebooks and Copilot Pages states that Copilot Notebooks requires a Microsoft Copilot or Copilot Chat licence. Copilot Pages, meanwhile, requires a OneDrive licence and an active OneDrive site. Check which feature you are trying to use before diagnosing an access or licensing issue.
The same documentation explains that notebooks are stored in a SharePoint Embedded container owned by the user. This container appears as “Loop” in administration tools. The distinction matters when locating the data in administrative tools: the interface used to open a notebook does not, by itself, describe where it is stored.
Inviting colleagues into a notebook makes it easier to work on a shared project, but does not remove the need to check the documents added and their permissions. Steve Goodman of Practical 365 recommends preparing data, permissions and protections before deploying Copilot. For more on using notebooks, see our article on creating and collaborating with Copilot Notebooks.
PowerPoint: test compliance with the brand kit
In PowerPoint, selecting a brand helps guide Copilot when creating a presentation. The strict brand adherence setting goes further: it instructs Copilot to use only the layouts and elements defined in the approved template rather than creating new layouts. It is intended for presentations whose visual structure needs to remain controlled.
Prepare the approved template
Include in the PowerPoint template the layouts Copilot should be able to use, particularly those intended for an opening, content and transitions.
Configure the brand kit
From the brand options shown in PowerPoint, go to select brand, then manage brand kits. Associate the template with the relevant kit and review the strict brand adherence setting.
Review a generated presentation
Generate a representative test presentation and check the layouts used, text, images and required elements. Restricting layouts does not constitute editorial or legal approval.
An organisation might set up separate kits for sales presentations and executive briefings. This is a configuration scenario, not a guarantee that Copilot will select the right kit on its own: selection and review are still necessary. Custom skills can also handle a repetitive task, such as adding a footer, but the example described shows that a configured skill can stop working as expected. Test it on a copy before incorporating it into a production workflow.
Excel: distinguish a summary of changes from restoration
In Excel, you can ask Copilot about changes to a workbook. In the example shown, a request for changes over the past six months returned a summary of changes to cells and sheet names. That period comes from the prompt used; it is not a guaranteed retention period for every workbook.
The summary helps direct a review: identify an unexpected change, then examine the workbook and its history. It should not be treated as a comprehensive audit log. In the example, a request to restore an earlier version did not succeed in Copilot; version history in OneDrive remains the suggested route for finding a previous version.
For a shared workbook, start with a targeted question about the period and changes you are looking for. Then confirm the changes using the available history features before attributing an action to someone or restoring a document.
Agents and skills: do not mistake a Frontier pilot for general availability
A skill groups instructions for a repetitive task. In the example of an agent that compares PDFs, one skill handles contracts and another can be prepared for sales proposals. This separation makes it possible to spell out the checks expected for each document type instead of loading every exception into a single instruction.
Adding skills to an agent is shown with a Frontier badge. The Microsoft Learn documentation on Frontier classifies these features as previews that may change. Access depends on administrator-managed enrolment and the assignment of a Microsoft Copilot licence to the user. The badge is therefore not a general availability date.
Frontier does not guarantee access for every user
Before training a team on an agent skill, check that pilot accounts can actually access it and allow for changes to its behaviour or interface.
A useful test is to give the agent a contract, then a sales proposal, and compare the checks applied in each case. Have it process an ambiguous document too: if it does not use the right skill, clarify the instructions and retain human review of the result. For more examples by application, see our actionable Copilot prompts in Microsoft 365.
Frequently asked questions
Can all Teams users see intelligent recaps?
No. Everyone can open Meeting Recaps, but intelligent text recaps require Teams Premium or a Microsoft Copilot licence. Video and audio recaps require a Microsoft Copilot licence; the app only lists meetings recorded or transcribed in the last 30 days.
Does a link to a Copilot conversation grant access to the documents it mentions?
No. The link shares a snapshot of the conversation without granting access to the files, emails or meetings it mentions. A recipient who continues the exchange works in a separate copy.
Can a Frontier feature be rolled out to every user?
Its presence in a pilot environment does not establish general availability. Microsoft classifies it as a preview; access depends on administrator-managed enrolment and a Microsoft Copilot licence assigned to each relevant user.
Start with a pilot with controlled access
First, choose a measurable use case: find a recap, share a reviewed response or create a presentation from an approved template. Confirm the result using the accounts and documents that will actually be used, rather than generalising from a single demonstration.
Checks before expanding the pilot
- Check the licences required for each type of recap and for notebooks.
- Review permissions for data cited or added in Copilot.
- Decide whether conversation sharing should remain enabled.
- Test PowerPoint templates and skills on working copies.
- Restrict Frontier features to enrolled, licensed users.
If your organisation handles confidential documents, start with permissions and sharing rules before promoting conversations or notebooks. If your goal is a compliant presentation, start with the approved template and a visual review.
Further reading
- Manage Meeting Recaps in Teams — to check licences, displayed meetings and supported platforms.
- Manage sharing of Microsoft Copilot conversations and responses — to review links and administrative controls.
- Check requirements for Copilot Pages and Copilot Notebooks — to distinguish licences, dependencies and storage.
- Prepare Microsoft 365 Copilot for real-world use — for more on preparing data and permissions.



