Seeking Guidance on Microsoft 365 Copilot Adoption Support for an Enterprise Customer
Hi Everyone, We are a newly enrolled Microsoft partner currently working with a customer to accelerate Microsoft 365 Copilot adoption across their organization. We are exploring how we can best support the customer and would like to understand whether there are any Microsoft programs, resources, partner managers, or engagement channels available to help us collaborate with Microsoft on Copilot adoption opportunities. Could anyone advise on: The recommended Microsoft channel/team to engage for an enterprise Copilot adoption opportunity Any Microsoft programs or resources available to support customer adoption How partners can collaborate with Microsoft for customer-specific Copilot adoption support Any guidance on the appropriate Microsoft team, program, or point of contact would be greatly appreciated. Thank you!Help.I have 365 Premium subscription, it hasn't expired, but I lost access to Copilot on phone.
I'm an Office 365 premium subscriber. I used to be able to use Copilot normally on Office on both my computer and iPhone, but now I can only use Copilot on Office on my computer. When I try to use Copilot on Office on my phone, it says: 'It seems you don't have a valid license. To get access, please contact your admin.' Before this problem happened, I sent an invite link to someone else to use Office 365 with me, and then I clicked the invite link myself on my phone using my subscriber account, and it showed that I successfully joined the sharing. After that, I couldn't use Copilot on Office on my phone anymore. Even though my subscription account is still shown as the organizer in the Family group and my subscription hasn't expired, it seems like I lost access to Copilot on my phone.
Excel Copilot fails when local workbook filename contains #
Excel Copilot does not work with locally stored workbooks whose filename contains the '#' character. The same workbook works correctly after renaming the file to remove '#'. The same workbook also works when stored on OneDrive with '#' in the filename. The issue appears specific to local files and filename parsing. Specifically, when clicking on Copilot in Excel, Copilot says "This file type is not supported for editing with Copilot. Please save this file as a modern file format, such as ".xlsx", to be able to edit it with Copilot." Interestingly, Copilot works fine if the Excel file name contains, for example, % or &, the problem only occurs if the name contains #. We suspect this is a bug. In our workflows, we work a lot with files that have # in their names and we would be very happy if this was indeed a bug and if it was fixed. Tnx.
