Copilot Excel error "Failed to fetch document context" - Cannot use paid service
Environment: Microsoft 365 (paid subscription, recently upgraded) Excel for Windows (desktop app) Copilot in Excel Issue: I am repeatedly receiving the error message "Failed to fetch document context due to an internal error" when trying to use Copilot in Excel. This error has been occurring for multiple days across multiple sessions. What happens: I open my Excel workbook (.xlsx file) I open Copilot from the ribbon I ask Copilot to perform a task (e.g., write data to cells, read from a table) Copilot responds as if it completed the task Nothing actually happens in my workbook — no data is written, no changes are made The error "Failed to fetch document context due to an internal error" appears What I've tried: Restarting Excel (multiple times) Closing and reopening Copilot panel Signing out and signing back in to my Microsoft account Checking for updates Waiting several hours/days and trying again Force-closing Excel via Task Manager Starting fresh chat sessions Contacted Microsoft Support chat (they directed me here) None of these resolved the issue. Impact: I recently upgraded to a paid subscription specifically to use Copilot I cannot use the service I paid for Simple tasks like writing text values to cells do not work Copilot claims tasks are "done" but nothing actually changes in my workbook This has been happening for 5+ days Questions: Is this a known server-side issue? Is there a fix or workaround? How can I get this resolved or request a refund for a non-functional service? Thank you for any help!Cloud PC Display Name Vs. Computer Name
I have seen a bit of confusion between Windows 365 Cloud PC Display Name Vs. Computer Name. I thought to create a quick discussion thread on this topic so that it can help the IT Community if there is any confusion at all. I have noticed different methods to change the Display names of Cloud PCs. Both the end-users and admins can change the display name of the Cloud PC. Even there are Graph API options to perform this action. The following is the Display Name of the Windows 365 Cloud PC, and end-users (w365 client portal) and admins can change this. This display name won't appear in any management tools such as Azure AD, Active Directory, Intune, SCCM, etc. (if I'm not wrong). The Windows 365 Business admin portal allows you to change the Display Name of the Cloud PC from the admin side. The Windows 365 Cloud PC computer name is another property that is part of the core operating system, such as Windows 10 or Windows 11. The computer name is a device property that Azure AD, MEM Intune, and third-party applications use as one of the primary identifiers of a Windows device. You can use the standard "Windows" methods to change the computer name of the Cloud PC, but I don't think this is supported for the Cloud PC scenario (am I wrong with this assumption?). So, I don't recommend renaming the computer name property of Cloud PCs for whatever reason. I have tested renaming the computer name of the Cloud PC, and it worked fine. I could still log in to Cloud PC. The name change got reflected in the management tools such as Intune and Azure AD. You have options to Export Windows 365 Cloud PC Names. I don't see any supported method to remotely change (mainly for the enterprise version of Cloud PC) the computer name of the Cloud PC from MEM Intune. The Cloud PC remote actions on the MEM admin center portal are different from remote actions for other devices. Thanks for the comments/confirmation from MS!Enterprise Security Assessment: A Strategic Lens for Mission Critical Environments
Understanding Enterprise Security at Scale Understanding security posture at scale requires more than isolated control reviews or point‑in‑time assessments. The Enterprise Security Assessment (ESA) helps organizations understand their security posture across Azure, Microsoft 365, and hybrid environments from a true enterprise perspective. Instead of assessing individual services or workloads in isolation, ESA provides a single, enterprise‑wide view of security. By examining identity, data security, endpoints, threat protection, and cloud infrastructure together, ESA helps uncover gaps that often span multiple teams and platforms. This broader perspective enables clearer prioritization, stronger alignment across security teams, and a more resilient foundation for long‑term security improvement. ESA complements other Microsoft assessments, such as workload‑specific reviews, by connecting the bigger picture - to align security priorities across teams and platforms, fostering a more cohesive and resilient security approach. From Standard Engagement to Strategic Partnership An Enterprise Security Assessment is typically delivered as a focused engagement designed to establish an enterprise‑wide view of security posture. At Microsoft, we begin by reviewing Secure Score insights, analyzing a defined set of core security datasets, and correlating those signals across Azure and Microsoft 365. For many organizations, this approach works well. Collecting and evaluating these datasets provides a high‑level understanding of security posture, highlights common gaps, and identifies priority improvement areas. In standard enterprise environments, ESA delivers actionable insights with minimal disruption and sets a solid foundation for security improvements. How ESA Evolves in Mission‑Critical Environments In large or mission‑critical environments, security is often distributed across multiple teams and tools. Operational constraints, regulatory requirements, and business dependencies introduce complexity that standard assessments cannot fully capture. For mission‑critical customers, ESA goes beyond a baseline review and becomes more consultative. This typically includes: 📝 Structured discovery sessions across multiple security domains 🤝 Deep‑dive workshops with specialized teams 🎯 Validation of findings against real‑world operating models 🔄 Iterative analysis to validate findings against real operational conditions This ensures recommendations reflect how security is actually managed, not just how it is documented. Why Going Deeper Matters to Customers For organizations operating at scale, this consultative ESA approach delivers significantly more than a standard readout: A realistic, enterprise‑wide understanding of security posture, grounded in actual configurations and operating models Clear visibility into cross‑team dependencies and systemic risks Prioritized recommendations aligned to existing licenses, third‑party tools, and regulatory requirements A realistic, phased security roadmap focused on adoption, not theory The result is a clear starting point for security improvements that teams can execute with confidence. A Continuous Improvement Model ESA is not a one‑time exercise. For most customers, it becomes the foundation for ongoing security maturity. Once a baseline is established, future ESAs are faster and more efficient, allowing organizations to track progress, validate improvements, and maintain alignment as environments evolve. Over time, ESA functions as an annual enterprise security health check, supported by follow‑up reviews and continuous improvement. In mission‑critical environments, this means: The first ESA requires deeper engagement investment Building cross-team alignment takes time Future assessments become smoother and more efficient once a baseline is established Over time, ESA functions as an enterprise security health check that supports continuous improvement. It works best when treated as a starting point for continuous improvement, and Enterprise Security Alignment. What Customers Gain from an Enterprise Security Assessment A true enterprise view Visibility across identity, data, devices, cloud workloads, and threat signals - without losing sight of critical details. A customized security roadmap Recommendations aligned to existing licenses, third‑party tools, hybrid footprints, and regulatory requirements - making adoption realistic, not aspirational. Momentum and measurability Many organizations track progress using dashboards or scorecards to measure improvement and sustain focus over time. Repeatability Once a baseline is established, future ESAs become easier and more efficient - serving as a regular health check rather than a brand‑new effort. A consultative model ESA delivers far more value than a one‑time assessment by fostering collaboration, shared understanding, and long‑term alignment. A Foundation for Continuous Improvement Enterprise security is complex, especially at scale. In mission‑critical environments, security success depends on embracing complexity, aligning teams, and moving beyond a standard assessment playbook. An Enterprise Security Assessment is more than a snapshot. It’s an opportunity to build alignment, inform strategy, and create a resilient security foundation that evolves with the organization.
Streamlining PDF and Image workflows on Cloud PCs without installing local software.
Hello everyone, I’ve been exploring ways to optimize document workflows within the Windows 365 environment, especially for tasks that usually require heavy desktop software like PDF editing or financial modeling. To solve this, I’ve been developing and using a suite of browser-based utilities at https://pdfcraftor.com/ I'm curious to know what other lightweight or web-based tools you all are using to keep your Windows 365 setup clutter-free? Would love to get some feedback on this approach!Incident critique : Edge Sync “Uninitialized”, appareils disparus, identité WAM/MSAL corrompue
Bonjour, Je rencontre un incident critique affectant directement mon identité Microsoft (MSA). Il ne s’agit pas d’un problème local mais d’un dysfonctionnement côté serveur. Voici les éléments techniques constatés : - Le conteneur Edge Sync de mon compte est en état “Uninitialized”. - Tous mes appareils ont disparu de mon compte Microsoft (Device Registration cassé). - Les services d’identité WAM / MSAL / OneAuth ne se réinitialisent plus correctement. - Impossible de créer de nouveaux passkeys ou d’utiliser les services dépendants de l’identité cloud. On dirait que ça nécéssite une intervention côté serveur : réinitialisation des identités WAM/MSAL, du conteneur Edge Sync, et du Device Registration. Je reste à l'écoute de toute aide en vous remerciant par avance.Expanding the Reach of AI-enabled Cloud PCs for Frontier Firms
Co-Authored by Lakshmi Rayasam Over the past several months, we’ve been focused on a clear goal: making AI-enabled Cloud PCs easier to adopt, easier to deploy, and available to more customers—wherever they are. Following the momentum from Ignite, releasing Improved Search & Click to Do, we’ve continued to evolve the AI-enabled Cloud PC experience in Frontier Preview, prioritizing scale, accessibility, and product market fit. The latest set of enhancements removes deployment blockers and expands where—and how—customers can get started. We’ve also added a new refreshing AI-enabled end-user experience explaining the value of Frontier while users hover over the AI-enabled (Frontier) tag. Note: Future availability of these features is dependent on the results of this Frontier Preview and is subject to change Removing the need for Windows Insiders AI‑enabled Cloud PCs now work with standard Windows 11 retail builds, eliminating the need for Windows Insider participation. This change alone unlocks broader enterprise deployment scenarios and removes a major barrier for production use. AI-enabled Cloud PCs are just one toggle away as IT admins can join our Frontier Program and enable AI-enabled Cloud PCs via a newly introduced policy setting within the Devices – Onboarding: Windows 365 > User Settings blade, and further filter access based on Microsoft Entra ID group access. Note: After enrolling the latest Windows 11 25H2 (OS Build 26200.7840 or higher) you must reboot your Cloud PC. Expanded regional availability To meet customers where they operate, we’ve expanded AI‑enabled Cloud PCs to additional Azure regions:‑ Japan East Germany West Central South Central US Canada Central This expansion improves latency, supports data residency needs, and enables more global customers to participate in the Frontier Preview. 128GB disk support for Windows 365 Enterprise We’ve added support for 128GB disk size Windows 365 Enterprise licenses, offering greater flexibility for customers who don’t require larger footprints while still enabling AI‑driven workflows. These right‑sized deployments and makes it easier to scale across broader user populations. Together, these updates directly address the most common Ignite feedback and are expected to unlock large‑scale deployments, including enterprise pilots transitioning into sustained usage. What Comes Next Following the March rollout, our CY26 focus shifts to closing parity gaps using cloud‑based models, in close partnership with Windows platform teams. Initial work centers on enabling Text Actions for Click‑to‑Do via a cloud models within Frontier Preview—one of the most requested capabilities from customers.‑‑‑ In parallel, we’ll continue investing in foundational improvements that increase perceived feature depth and usage signals, including cost optimization, reliability enhancements, and productivity scenarios that compound value across the Cloud PC experience.
Windows NVMe-oF Initiator connect error
Hi everyone, I am trying to test the new Windows NVMe-oF Initiator within build 29550.1000 but I am not able to connect to a remote storage array - getting the error "IOCTL_NVMEOF_CONNECT_CONTROLLER failed with error code 0x1f" (see screenshot). Any idea what does this error mean or what can be wrong?
