Helping users navigate the rebrand to the "Microsoft 365 Copilot" App

This app/experience was formerly known as the Microsoft 365 App or by many just as the Microsoft 365 homepage (especially in the context of the browser and URLs like Microsoft365.com). Now that it's been rebranded to the Microsoft 365 Copilot app, I'm curious to know how peers are adapting their support for end users in regards to this change. 

If you want users to head to this app or web location to use Copilot Chat (in one of its forms - web or work) there isn't really much issue ("Go to the Microsoft 365 Copilot app to use Copilot"). But what these other scenarios? 

• In the browser/or desktop app
  • "Go to the Microsoft 365 Copilot app to modify your M365 Profile
  • "Go to the Microsoft 365 Copilot app to download the desktop Office apps" 
  • "Go to the Microsoft 365 Copilot app to access PowerPoint in the browser. 
• In the mobile app
  • "Go to the Microsoft 365 Copilot app to update that PPT you've been working on while you're in an Uber." 
  • "Go to the Microsoft 365 Copilot app to capture pics of whiteboards and add them to your OneDrive" 

All these scenarios really have nothing to do with Copilot, but you've got to use the Copilot app...a little awkward right? (p.s. trying not to incent a riot about MSFT's naming skills) What makes it downright silly is if you've suppressed Copilot all together for users for whatever reason, right? To my understanding even if you've blocked Copilot Chat in your org, this app is still called Microsoft 365 Copilot... 

If I've misunderstood anything about the situation, please educate me. Otherwise, I'd love some thoughts on the group on how you are or are thinking about navigating this awkwardness with users.