Yes, Microsoft Copilot can be safe for client data at work when your brokerage uses the protected business service and controls access to client files. A personal Copilot account has different terms. Enterprise data protection also does not fix a SharePoint folder that every employee can already open.
Before rollout, identify the account and licence your staff use. Then test whether the right people can access the right loan files, including through Copilot.
Which Copilot Are You Using?
The account and licence determine which Copilot protections and work-data features apply. The word “Copilot” on a button is not enough to identify either.
Copilot Products Compared
| Experience | Account and access | What it means for client data |
|---|---|---|
| Free consumer Microsoft Copilot | Personal Microsoft account or consumer experience | Consumer privacy terms apply. Conversation activity can be used for model training, subject to settings and exclusions. Keep identifiable client files out of this service. |
| Microsoft 365 Copilot Chat | Work account with a qualifying Microsoft 365 subscription | Enterprise data protection applies. Without the paid Copilot add-on, access to work content is more limited, including files supplied to the chat and supported application context. |
| Paid Microsoft 365 Copilot | Work account with the Copilot add-on assigned | Enterprise data protection applies, with broader work-data features across permitted emails, meetings and files. Permissions and configuration still govern access. |
Microsoft’s consumer Copilot privacy FAQ explains its training settings and data uses. Turning off consumer model training does not give a personal account the brokerage’s business contract or administrative controls.
Microsoft’s Copilot licence comparison distinguishes the work service with and without an add-on. Product and interface names change, so confirm the assigned licence in your organisation’s Microsoft 365 administration settings.
Enterprise Data Protection Explained
Enterprise data protection means the business Copilot services operate under Microsoft’s commercial data-protection commitments. Microsoft acts as a data processor for the organisation under the applicable contract.
Microsoft says prompts and responses are not used to train foundation models. The same protection covers work data retrieved through Microsoft Graph, the service connecting Microsoft 365 content. These commitments apply to the protected work experience, rather than every product carrying the Copilot name. Microsoft’s enterprise data protection guidance sets out the distinction.
Copilot does store data. Microsoft’s privacy documentation says activity history includes prompts and responses, with citations to grounding information. Administrators can manage retention and compliance searches through Microsoft Purview. A no-training promise is separate from a no-storage promise.
For Australian tenants, Microsoft’s data location FAQ lists Australia among the countries covered by Microsoft 365 Copilot’s Product Terms data-residency commitments. These address data at rest. Have your administrator confirm the tenant’s actual data location and any Multi-Geo configuration before promising Australian storage to clients.
Storage location is also separate from where an AI model processes a request. Microsoft’s privacy documentation allows worldwide traffic to be processed across regions. Treat any requirement for Australian-only processing as a separate configuration and contractual check, including the models and agents enabled.
Web search needs its own decision. Copilot can generate a search query from a prompt and send it to Bing under separate data-handling terms. User and tenant identifiers are removed, but that does not mean every confidential detail is removed from the query. Disable web search for confidential work where the brokerage cannot accept that disclosure path.
Copilot Sees What Your Staff Can See
Copilot’s work-data access follows the user’s existing permissions. It can surface eligible content a staff member is allowed to read, even if that person did not previously know where it was stored.
Microsoft’s data-protection architecture explains how SharePoint and OneDrive controls affect discovery. Copilot does not grant a staff member permission to a restricted client folder. However, a broad staff group can already give that person access before Copilot is introduced.
Consider a hypothetical brokerage where all staff can read a SharePoint library of client bank statements. A new assistant asks Copilot about a client’s expenses. The existing permission can make those statements available to the assistant’s work-data responses, despite the owner intending access for the assigned broker only.
Review inherited folder access and old sharing links alongside site membership. Check OneDrive shares from former team arrangements as well. Changing the Copilot licence does not correct those permissions.
Sensitivity Labels and Permissions to Fix First
Fix access before assigning Copilot broadly, then apply sensitivity labels with protection settings that match the client information. A label’s name alone does not restrict who can read a document.
Your administrator needs the relevant Microsoft Purview roles and licences for the controls selected. Use a pilot with fictional client information to check the result before enabling wider use.
- Review the client-data locations. In SharePoint and OneDrive, inspect who can access each library or folder. Remove unnecessary membership and replace broad sharing links with access for the staff handling that client. Confirm an unrelated staff account cannot open the pilot file directly.
- Create or reuse the client-data label. In Microsoft Purview, open Solutions > Information Protection > Sensitivity labels. Configure a suitable label for files and emails, with encryption permissions where access restrictions are required. Publish it through the appropriate label policy so the pilot users can apply it. Follow Microsoft’s label creation and publishing procedure.
- Apply protection to the actual files. Enable sensitivity-label support for SharePoint and OneDrive files, then label the supported documents in the client folders. For a PDF bank statement, confirm that PDF protection is enabled and the protection works on that file type.
- Check the difference between site and file labels. A label applied to a SharePoint site can control site-level settings. It does not automatically label or encrypt the documents inside it. Microsoft’s workspace label guidance explains this boundary. Check a sample document’s own label and access settings.
- Limit discovery during cleanup. Where licensed, use Restricted Content Discovery for SharePoint sites still under review. In the SharePoint admin centre, select the site under Sites > Active sites. Open Settings and enable Restrict content from Microsoft Copilot. This limits discovery and does not revoke existing access. It is not a OneDrive control.
- Verify the pilot with two accounts. The assigned broker must be able to open the fictional client file and use an approved Copilot task. An unrelated staff member must be unable to open it or retrieve its contents through Copilot. Check direct access as well as Copilot answers, because an answer omitting a file does not prove access is blocked.
If a label is missing from an application, inspect the publishing policy and whether it includes the user. Allow policy changes to propagate before testing again. If the wrong person can read the file, repair access and encryption permissions before expanding the pilot.
Is Copilot Safe for Confidential Information?
Yes, business Copilot can handle confidential information under enterprise data protection when the brokerage has approved the use and configured access correctly. Paying for the add-on expands work-data capabilities. It does not certify the brokerage’s permissions or make every proposed use appropriate.
Microsoft supplies service security and commercial data-protection commitments. The brokerage controls which staff can reach a client’s loan file and which information they enter into a prompt. A secure service can still return confidential information to someone whose access is too broad.
Remaining risks include compromised staff accounts, misleading instructions hidden in retrieved content and staff forwarding an answer outside the client team. Agents introduce additional data-handling terms. Copilot can also produce an incorrect summary, so a broker must check financial figures against the source before relying on them.
Approve a specific task, such as summarising an authorised client’s existing correspondence. Verify access with fictional files and record the settings that make that task acceptable. Expand access only after the pilot confirms both the permitted use and the blocked use.
