NewB here...Wanting to understand the steps to Implement M365 Copilot

Hi CLitz,

As you will see, I agree with NicolasKheirallah,

Implementing Copilot is a substantial project; it's far more complex than simply flipping a switch. A crucial aspect of its deployment involves data and content tagging. To address your query, if the data or content is meaningful for the entire organization, it will similarly benefit Copilot. Like for any of us, Copilot performs optimally when the context is unambiguous. This involves several key steps:

• Tagging content with relevant keywords.
• Organizing content into logical folders and sites.
• Retaining only the most recent versions of documents to avoid duplication.
• Removing redundant, outdated, or trivial (ROT) content.
• Adhering to a standardized naming convention for files.

This content could include various formats like files, emails, chats, wikis, pages, databases, etc. Appointing a data steward is a strategic investment for ensuring quality and success.

It appears you are in the process of evaluating the acquisition of licenses. May I suggest to initiate a high-level discussion within your leadership for commitment and establishing a Center of Excellence as foundational steps if not already done ?

The implementation of Copilot for Microsoft 365 involves multiple facets:

• Establishing a Center of Excellence (CoE).
• Managing change, as this technology can significantly alter workflows for employees and businesses.
• Coordinating project management.
• Conducting thorough analysis.
• Engaging with partners/providers, who may already be developing solutions.
• Handling security, access control, and compliance.
• Providing training and knowledge transfer.
• Involving programming expertise.
• Raising awareness about the new system.
• Popularizing the tool within the organization for maximum adoption and impact.

Source: Prepare your data for searches in Copilot for Microsoft 365 - Training | Microsoft Learn

Feel free for asking if you need further information,

CLitz 

So first off right of the bad you need atleast 500+ E3 or E5 Licenses which I'm guessing you have!

As for best practices, I would recommend that you check your data quality! So what I mean with data quality is:

• That you have files that are relevant! Clean up as much old junk as possible. It is truly bad data in -> bad data out if you don't clean up
• Look over the whole architecture of your sites and data. Look into Hubsites and Sites in Sharepoint
• Tag files and documents who as much relevant information as possible in document libraries and lists! Also make use of the term-store
• You want to implement sensetivity labels and retention policies! This also means that you need to tag the information with the correct tags!
• You also need to check permissions and that users have access to what they should have access to and not. Implement some form of access review
• You might want to exclude some data considering you're in healthcare and patient data can be sensitive, look into what laws and stipulations exist.

A lot of these are organisational specific and also industry specific, for example sensetivity labels and retention policies for a health care organisation will differ a lot from manufacturing industry!

I would recommend you to talk to you Microsoft CSAM/CSM and see what support you can get in form of pilot and workshops from partners