The importance of a centralised M365 tenant
In today’s fast-paced business environment, staying ahead of the curve means embracing the transformative power of AI. Microsoft is leading the AI charge with Copilot: a revolutionary tool designed to enhance productivity and streamline operations in the workplace.
In this series of blog posts, we’re taking a deep dive into the world of AI and Microsoft Copilot. For our second blog in the series, Matt Dunkin, COO at AspiraCloud, discusses the value of migrating to a central Microsoft 365 tenant prior to adopting Microsoft Copilot.
Read on:
Why migrate to a single Microsoft 365 tenant?
AspiraCloud has long championed centralising multiple tenants to one, single platform. From improving security, simplifying IT environments, to potential cost savings and focusing on a Cloud First strategy, operating a single tenant per organisation keeps all your data, documents and other information safely in one place.
For organisations looking to adopt Copilot for Microsoft 365, having a single tenant in place is more important than ever. Why? Because Copilot for Microsoft 365 is enabled in your tenant and following a Copilot purchase and license assignment, it will automatically create a semantic index of all your content before it starts to work efficiently. (See our first blog to understand more about Copilot for Microsoft 365 as opposed to Copilot in Microsoft 365)
What is a semantic index?
Semantic index is an indexing map of all data within your tenant which triggers automatically after Copilot has been purchased. That’s every email, Teams conversation and every document you have access to, within the tenant boundary. According to the Microsoft 365 Commercial Support Team, the indexing process at the tenant-level works through about 95% coverage of OneDrive and SharePoint Online text-based documents within a week, with full coverage taking up to 28 days.
Why Copilot for Microsoft 365 works best with a single tenant
Whilst Copilot for Microsoft 365 can be extended to talk to other services, such as your CRM or MIS as well as access to the Internet, it can only use Microsoft 365 data stored in its current tenant. It respects labelling and permissions, but if you have other documents that are stored on other external SharePoint sites or Teams folders, this data will not be visible to Copilot. This is why a single tenant is crucial for Copilot to work at optimum level and return the best results.
What if you want to use Copilot with a Multi-Tenant Organisation?
If you are considering a Multi-Tenant Organisation (MTO), then I would strongly review whether Copilot for Microsoft 365 will ever be effective in that environment. There is a very clear security boundary within the single tenancy and whilst the other product groups have started making things work, it’s very difficult to see how Copilot could ever work.
AspiraCloud has always believed that an organisation works better with a single production tenant and we have already delivered many migration projects to support this philosophy. Copilot for Microsoft 365 delivers another very strong supporting argument for a centralised tenant – and may even be the cherry on top!
If you would like to learn more about a single tenancy and how you can become Copilot ready, simply contact us.