SharePoint Online and Power Platform Deep-Dive Session
Global consumer goods company
In short
What should you check in SharePoint before Copilot starts searching it?
Sites that grow without a plan end up with mixed branding, unclear permissions and guests who can reach more than intended. Copilot adds a new question: what will it find, and who can ask it? We ran a deep-dive session for the client covering both.
At a glance
- Five SharePoint topics in one session
- Copilot shown across five Power Platform products
- Permissions and external sharing covered
The client
The client is a global consumer goods company with operations worldwide. The session was run for its SharePoint and Power Platform stakeholders and dated February 2024.
What it was costing them
- Inconsistent branding: sites built one at a time look different and are hard to trust.
- News that stays unread: updates posted to SharePoint do not reach the inbox where staff work.
- Permission sprawl: Teams, group and standalone sites each manage access differently.
- External sharing risk: guest access and sharing links without a clear policy leave documents exposed.
What we built
The session walked through five SharePoint topics, followed by Copilot across the Power Platform.
- Consistent sites: themes, site templates and hub sites show how to brand once and reuse.
- News that reaches people: news templates, newsletters and news in Outlook, plus Stream and Clipchamp for video.
- Clear access rules: permission models compared across standalone, group and Teams-connected sites.
- Safer guests: guest settings across Entra ID, groups, Teams and SharePoint, with sharing policies and auditing.
- Better lists: conditional and JSON formatting, plus Power Apps canvas forms.
- Copilot by product: how Copilot helps in Power Apps, Power Automate, Power BI, Power Pages and Copilot Studio.
Results
- Result: stakeholders left with one shared view of how sites, news, permissions and guests should be set up.
- Result: a short list of next steps, such as a site template standard and a review of external sharing.
- The session covered five SharePoint topics and five Copilot scenarios, as set out in the agenda.
The risk most teams miss
Copilot only uses what a user can already open. If permissions have drifted, it will surface that content in answers. The session therefore put permissions and sharing before Copilot, and we start any follow-up with an oversharing review.
What we would add today
Improvements we would add on top of what is live.
- Add SharePoint Advanced Management for site access reviews before Copilot is widened.
- Use sensitivity labels on sites and Teams, so sharing rules follow the label, not the owner's memory.
- Build a Copilot Studio agent grounded on intranet policy libraries to answer branding and sharing questions.
Technology
SharePoint Online, Microsoft 365, Entra ID, Stream, Clipchamp, Power Platform, Copilot Studio, Microsoft 365 Copilot.
Tell us how your sites and guests are managed today, and we will tell you where your biggest risk sits.
Products and capabilities
- SharePoint
- Microsoft 365 Copilot
- Power Platform
- site governance
- external sharing
- permissions
The service behind this work
Power Platform governanceThe service behind this work
Copilot and agent readinessMore on this industry
Manufacturing and distribution
Related use cases
IT and platform teamsDataverse Housekeeping and Storage Advice
Dataverse capacity costs money, and it fills quietly. Import logs, system jobs and old workflow records grow in the background until an environment runs short. The client asked how to housekeep its environments. We put in place a short routine of checks and clean-ups that frees storage without touching business data.
Power Platform Governance Kickstarter and Handbook
The client held more than 2,000 per-user Power Platform licences, yet had no agreed way to open an environment, approve a connector or hand an app to IT. Each request was decided from scratch. We ran five governance workshops and wrote the strategy and handbook that make those decisions repeatable.
- c. 180
- handbook pages
- 2,000+
- per-user licences
Service Desk App with Structured Tickets and SLAs
A shared mailbox is a poor ticket system. Support staff cannot tell which request is being worked on, who owns it or which matters most, so urgent and old requests wait. We built a service desk app that turns each request into a ticket with a status, an owner and a deadline.
Have a Microsoft project in mind?
Tell us what you need built, fixed or supported. A senior consultant replies within one business day.