Microsoft 365 Copilot design and architecture

I am struggling to find how Data is processing in data at rest and transmit in copilot architect? Do you have any idea ?

Laxman V Sure let me explain. If you are using CoPilot as part of M365, and we use one example where we are just using CoPilot to chat with our data.

1: The end-user sends a prompt "How much vacation am I entitled during summer?" into Copilot
2: CoPilot will then alter the prompt with its own system message, not sure of the specifics here, but that one we will know more about later. 

2: The Copilot service will then trigger a search using the Microsoft Search service, which will then in turn use the Semantic Search Index to try and find data that is similar to the initial prompt. The search here is similar to the capabilities that are present today in Microsoft 365 with regular search. All search is done in the context of the access that the user has. 

3: The service will then present results with the data that might provide answers to the initial prompt
4: The results and data are then sent trough the Azure OpenAI service for Copilot which then generates a response back to the user. "you are entitled to X amount of days, based upon these sources" 

So much of the capabilities is powered by Microsoft Search, which gets information from the prompt and the results are then processed trough the OpenAI LLM. So data that is presented to the user is only data that the user has access too.