MICROSOFT PRODUCT CAPABILITIES
Connect useful AI to the work.
Microsoft Copilot experiences differ by licence, application, and the information they can use. Copilot Chat provides an entry point with eligible Microsoft 365 subscriptions. Licensed work grounding adds organisational context through Microsoft Graph and Work IQ, within the user’s existing permissions.
Chat and research
Ask questions, work with provided files, and prepare responses using the sources available to the selected Copilot experience.
Microsoft 365 applications
Use supported assistance in applications such as Word, Excel, PowerPoint, Outlook, and Teams. Access, integration depth, and priority vary by licence and tenant configuration.
Pages, notebooks, and agents
Develop shared content, work with selected reference material, and use suitable agents. Custom and work-data agents can have additional usage charges.
Administrative control
Manage access, data permissions, application settings, and adoption. Copilot respects existing access; it does not repair overshared documents or unreliable source information.
Choose the experience before allocating licences
Separate included chat access, full work grounding, in-app requirements, and agent usage. Use the current Microsoft licence guide to match each role rather than treating every Copilot feature as one entitlement.
Put it to work with Braintree.
Braintree identifies practical use cases, reviews tenant and information readiness, configures the rollout, and helps teams build and measure useful working habits.
01
Identify the work before choosing the Copilot route.
A useful AI brief names the task, its inputs and the person who checks the result. Summarising a meeting, preparing a first draft from approved documents and answering a question across a knowledge base are different requirements. They may use different products, permissions and levels of customisation. Begin with a small set of recurring tasks that your team can evaluate consistently.
Microsoft 365 Copilot brings assistance into the Microsoft 365 working environment. Copilot Studio is a tool for building and managing agents and workflows connected to knowledge and business systems. A custom Azure AI application has its own engineering and operational scope. Treat these as related routes with different delivery requirements, rather than one interchangeable licence.
02
Readiness needs technology, content and business ownership.
Owner
Evidence needed
IT and identity
The proposed users, qualifying licences, Entra accounts, mailbox location, supported applications and network access.
Information owners
Authoritative documents, current permissions, content that is duplicated or obsolete, and information that requires restricted access.
Business sponsor
The task baseline, accepted quality standard, human review point and the people available to trial the workflow.
Agent or application owner
For custom work, approved knowledge sources, integration access, allowed actions, operating costs and support responsibilities.
03
Measure usable work, including the review effort.
A pilot should use examples from the selected roles and include difficult cases: incomplete source material, conflicting documents and a question the system should not answer. Record whether the output is correct, whether its sources are useful and how much editing is needed. Counting prompts alone does not show whether the work improved.
Microsoft states that organisational information surfaced by Copilot follows the user’s access permissions. That makes permission quality an input to deployment. Content that was already shared too broadly can remain discoverable. Review access and content ownership alongside rollout planning, and keep generated output subject to the appropriate human review.
For an agent that can take action, define the action separately from the answer. Reading an order, changing an order and communicating with a customer carry different consequences. Agree authentication, approval points, exception handling and a named owner. Braintree readiness, configuration, training or custom development should be stated as deliverables in the proposed engagement.
EVIDENCE & DOCUMENTATION
See the work in context.
BEFORE YOU DECIDE
