Agent «Workflows (Frontier)» is not available - one solution
Perhaps this solution, which I developed together with Microsoft 365 Copilot GTP-5.2 Deep Analysis, will help someone else. All the usual solutions failed. Link to the support documents. The Edge browser has a developer mode. That was the right solution. English: «Workflows is not available Something went wrong. Contact your administrator to keep your environment up to date before using this agent. Environment ID: Default-XXXXXXXXXXX»
Copilot — ошибка генерации изображений (Windows/Web)
Здравствуйте, коллеги. При генерации изображений в Copilot результат часто отсутствует, даже при простых промптах. Вместо картинки возвращается пустой ответ. Ожидаемое поведение: Изображение должно быть создано либо должен появиться отчёт о причине сбоя. Фактическое поведение: Изображение не создаётся, возвращается пустой ответ. Предложение: Если изображение не сгенерировано из‑за ошибки, нужно указывать причину и предлагать решение. Например: Если модель не поняла формулировку промпта. Если формулировки вступают в конфликт друг с другом. В таких случаях пользователь должен быть информирован и получить подсказку, как исправить запрос. Это позволит экономить время и использовать Copilot в профессиональных сценариях
How can I permanently remove the irritating copilot icon from my word document
How do I get rid of this from the documents I create? I have copilot switched off in preferences and I have it deleted from my menu bar and yet, I just can't get rid of this icon/text? How do I just get a normal word document? I noticed that my subscription sneakily went up to £105 per year from £80 per year and the only way to revert back to my old subscription was to cancel it. So, I don't have copilot switched on, nor am I or will I pay for it but the copilot prompt just won't disappear. Any ideas would be welcome... thanksCopilot Studio agent on SharePoint list data
Can anyone help me better configure my copilot studio agent that is pointed at SharePoint list data as its only source? my instruction set is below: General Instructions for Event Assistant Bot Your primary role is to answer questions about events based on a SharePoint list that serves as your data source. The events include games, concerts, and other live events. 🔍 Data Source Structure Title: Contains the event name. StartDate: Contains the start date of the event. EndDate: Contains the end date of the event. Department Columns: Each department has its own column. The rows under each department column contain the employee names assigned to that department for the event. 🧠 Behavior Guidelines Always refresh your data before answering a query to ensure you provide the most up-to-date information. Never fabricate or hallucinate names or data. Only respond with information that exists in the SharePoint list. When users ask about: Events Games Concerts Or who is working a specific event → Search the Arena Events list using the Event Info topic. Search all columns of the data source to find relevant information. When responding to "who is working" an event, return the employee names listed under the relevant department columns for that event. 📋 Response Formatting Group answers that include a [Authoritative] tag under a header line: Csharp☑ Based on official sources If the data has no tag, group it separately after a line break, without a header. 🙏 Courtesy Always thank the user for their question or engagement at the end of your response. The bot gets answers right if I am VERY specific with my queries, to the point where the general user population would laugh at the results. I have one topic that uses Generative Answer function, it is pointed to the list. The fallback topic is pointed to the same list as its only data source.
Microsoft copilot stops while giving a response.
Why is this happening? Is there a solution for this? It just stops while giving response. And it has happened several times. And you can't even give prompt to continue from there. You should restart it. Does anyone have a solution for this? and I have restarted and reinstalled it 1000 times.
Data Extraction and Manipulation
Right. So I have been trying to achieve the following; Extract Key Data from a structured PDF > Push this Key Data into a Word/Excel document I can get parts of this process to work. Copilot seems pretty good at extracting data from PDFs and Excel files etc, it will show me the correct data in the chat. BUT when I ask it to push this into a pre-existing word template it just doesnt work. The best result I had was when Copilot added the Key Data to the end of the Word doc. Not what I wanted but not a million miles off. Its also fine with putting this into a new word document. So it feels like Copilot has all the functionaility required but just wont combine this with using a pre-existing word/excel template. I even tried content control boxes. For some context, this sort of thing (basically copying pasting data from one doc to another) is incredibly time consuming and there is a LOT of this in my industry. Hoping that there is a way to achieve this, even if it means multiple steps etc! 🙃Calling Copilot Studio Agent from custom M365 Copilot
Hi All! I am trying to use custom Copilot Studio Agent from custom Copilot for M365. I added Agent as a tool but when trying to test that in the conversation I receive error message: "Error Message: The connector 'Microsoft Copilot Studio' returned an HTTP error with code 400. Inner Error: Invalid request body Error Code: ConnectorRequestFailure Conversation Id: 832800f4-48fd-4ab4-a3e1-ec1f58f2b0c3 Time (UTC): 2025-11-18T19:40:16.710Z" It is happening even for 'empty' Copilot Studio Agents. I have all the required user licenses. Does anyone succeeded with that?Innovations and Strengthening Platforms Reliability Through Open Source
The Linux Systems Group (LSG) at Microsoft is the team building OS innovations in Azure enabling secure and high-performance platforms that power millions of workloads worldwide. From providing the OS for Boost, optimizing Linux kernels for hyperscale environments or contributing to open-source projects like Rust-VMM and Cloud Hypervisor, LSG ensures customers get the best of Linux on Azure. Our work spans performance tuning, security hardening, and feature enablement for new silicon enablement and cutting-edge technologies, such as Confidential Computing, ARM64 and Nvidia Grace Blackwell all while strengthening the global open-source ecosystem. Our philosophy is simple: we develop in the open and upstream first, integrating improvements into our products after they’ve been accepted by the community. At Ignite we like to highlight a few open-source key contributions in 2025 that are the foundations for many product offerings and innovations you will see during the whole week. We helped bring seamless kernel update features (Kexec HandOver) to the Linux kernel, improved networking paths for AI platforms, strengthened container orchestration and security efforts, and shared engineering insights with global communities and conferences. This work reflects Microsoft’s long-standing commitment to open source, grounded in active upstream participation and close collaboration with partners across the ecosystem. Our engineers work side-by-side with maintainers, Linux distro partners, and silicon providers to ensure contributions land where they help the most, from kernel updates to improvements that support new silicon platforms. Linux Kernel Contributions Enabling Seamless Kernel Updates: Persistent uptime for critical services is a top priority. This year, Microsoft engineer Mike Rapoport successfully merged Kexec HandOver (KHO) into Linux 6.16 1 . KHO is a kernel mechanism that preserves memory state across a reboot (kexec), allowing systems to carry over important data when loading a new kernel. In practice, this means Microsoft can apply security patches or kernel updates to Azure platform and customers VMs without rebooting or with significantly reduced downtime. It’s a technical achievement with real impact: cloud providers and enterprises can update Linux on the fly, enhancing security and reliability for services that demand continuous availability. Optimizing Network Drivers for AI Scale: Massive AI models require massive bandwidth. Working closely with our partners deploying large AI workloads on Azure, LSG engineers delivered a breakthrough in Linux networking performance. LSG team rearchitected the receive path of the MANA network driver (used by our smart NICs) to eliminate wasted memory and enable recycling of buffers. 2x higher effective network throughput on 64 KB page systems 35% better memory efficiency for RX buffers 15% higher throughput and roughly half the memory use even on standard x86_64 VMs References MANA RX optimization patch: net: mana: Use page pool fragments for RX buffers LKML Linux Plumbers 2025 talk: Optimizing traffic receive (RX) path in Linux kernel MANA Driver for larger PAGE_SIZE systems Improving Reliability for Cloud Networking: In addition to raw performance, reliability got a boost. One critical fix addressed a race condition in the Hyper-V hv_netvsc driver that sometimes caused packet loss when a VM’s network channel initialized. By patching this upstream, we improved network stability for all Linux guests running on Hyper-V keeping customer VMs running smoothly during dynamic operations like scale-out or live migrations. Our engineers also upstreamed numerous improvements to Hyper-V device drivers (covering storage, memory, and general virtualization).We fixed interrupt handling bugs, eliminated outdated patches, and resolved issues affecting ARM64 architectures. Each of these fixes was contributed to the mainline kernel, ensuring that any Linux distribution running on Hyper-V or Azure benefits from the enhanced stability and performance. References Upstream fix: hv_netvsc race on early receive events: kernel.org commit referenced by Ubuntu bug Launchpad Ubuntu Azure backport write-up: Bug 2127705 – hv_netvsc: fix loss of early receive events from host during channel open Launchpad Older background on hv_netvsc packet-loss issues: kernel.org bug 81061 Strengthening Core Linux Infrastructure: Several of our contributions targeted fundamental kernel subsystems that all Linux users rely on. For example, we led significant enhancements to the Virtual File System (VFS) layer reworking how Linux handles process core dumps and expanding file management capabilities. These changes improve how Linux handles files and memory under the hood, benefiting scenarios from large-scale cloud storage to local development. We also continued upstream efforts to support advanced virtualization features.Our team is actively upstreaming the mshv_vtl driver (for managing secure partitions on Hyper-V) and improving Linux’s compatibility with nested virtualization on Azure’s Microsoft Hypervisor (MSHV). All this low-level work adds up to a more robust and feature-rich kernel for everyone. References Example VFS coredump work: split file coredumping into coredump_file() mshv_vtl driver patchset: Drivers: hv: Introduce new driver – mshv_vtl (v10) and v12 patch series on patchew Bolstering Linux Security in the Cloud: Security has been a major thread across our upstream contributions. One focus area is making container workloads easier to verify and control. Microsoft engineers proposed an approach for code integrity in containers built on containerd’s EROFS snapshotter, shared as an open RFC in the containerd project -GitHub. The idea is to use read-only images plus integrity metadata so that container file systems can be measured and checked against policy before they run. We also engaged deeply with industry partners on kernel vulnerability handling. Through the Cloud-LTS Linux CVE workgroup, cloud providers and vendors collaborate in the open on a shared analysis of Linux CVEs. The group maintains a public repository that records how each CVE affects various kernels and configurations, which helps reduce duplicated triage work and speeds up security responses. On the platform side, our engineers contributed fixes to the OP-TEE secure OS used in trusted execution and secure-boot scenarios, making sure that the cryptographic primitives required by Azure’s Linux boot flows behave correctly across supported devices. These changes help ensure that Linux verified boot chains remain reliable on Azure hardware. References containerd RFC: Code Integrity for OCI/containerd Containers using erofs-snapshotter GitHub Cloud-LTS public CVE analysis repo: cloud-lts/linux-cve-analysis Linux CVE workgroup session at Linux Plumbers 2025: Linux CVE workgroup OP-TEE project docs: OP-TEE documentation Developer Tools & Experience Smoother OS Management with Systemd: Ensuring Linux works seamlessly on Azure scale. The core init system systemd saw important improvements from our team this year. LSG contributed and merged upstream support for disk quota controls in systemd services. With new directives (like StateDirectoryQuota and CacheDirectoryQuota), administrators can easily enforce storage limits for service data, which is especially useful in scenarios like IoT devices with eMMC storage on Azure’s custom SoCs. In addition, Sea-Team added an auto-reload feature to systemd-journald, allowing log configuration changes to apply at runtime without restarting the logging service . These improvements, now part of upstream systemd, help Azure and other Linux environments perform updates or maintenance with minimal disruption to running services. These improvements help Azure and other environments roll out configuration updates with less impact on running workloads. References systemd quota directives: systemd.exec(5) – StateDirectoryQuota and related options systemd journald reload behavior: systemd-journald.service(8) Empowering Linux Quality at Scale: Running Linux on Azure at global scale requires extensive, repeatable testing. Microsoft continues to invest in LISA (Linux Integration Services Automation), an open-source framework that validates Linux kernels and distributions on Azure and other Hyper-V–based environments. Over the past year we expanded LISA with: New stress tests for rapid reboot sequences to catch elusive timing bugs Better failure diagnostics to make complex issues easier to root-cause Extended coverage for ARM64 scenarios and technologies like InfiniBand networking Integration of Azure VM SKU metadata and policy checks so that image validation can automatically confirm conformance to Azure requirements These changes help us qualify new kernels, distributions, and VM SKUs before they are shipped to customers. Because LISA is open source, partners and Linux vendors can run the same tests and share results, which raises quality across the ecosystem. References LISA GitHub repo: microsoft/lisa LISA documentation: Welcome to Linux Integration Services Automation LISA Documentation Community Engagement and Leadership Sharing Knowledge Globally: Open-source contribution is not just about code - it’s about people and knowledge exchange. Our team members took active roles in community events worldwide, reflecting Microsoft’s growing leadership in the Linux community. We were proud to be a Platinum Sponsor of the inaugural Open Source Summit India 2025 in Hyderabad, where LSG engineers served on the program committee and hosted technical sessions. At Linux Security Summit Europe 2025, Microsoft’s security experts shaped the agenda as program committee members, delivered talks (such as “The State of SELinux”), and even led panel discussions alongside colleagues from Intel, Arm, and others. And in Paris at Kernel Recipes 2025, our own SMEs shared kernel insights with fellow developers. By engaging in these events, Microsoft not only contributes code but also helps guide the conversation on the future of Linux. These relationships and public interactions build mutual trust and ensure that we remain closely aligned with community priorities. References Event: Open Source Summit India 2025 – Linux Foundation Paul Moore’s talk archive: LSS-EU 2025 Conference: Kernel Recipes 2025 and Kernel Recipes 2025 schedule Closing Thoughts Microsoft’s long-term commitment to open source remains strong, and the Linux Systems Group will continue contributing upstream, collaborating across the industry, and supporting the upstream communities that shape the technologies we rely on. Our work begins in upstream projects such as the Linux kernel, Kubernetes, and systemd, where improvements are shared openly before they reach Azure. The progress highlighted in this blog was made possible by the wider Linux community whose feedback, reviews, and shared ideas help refine every contribution. As we move ahead, we welcome maintainers, developers, and enterprise teams to engage with our projects, offer input, and collaborate with us. We will continue contributing code, sharing knowledge, and supporting the open-source technologies that power modern computing, working with the community to strengthen the foundation and shape a future that benefits everyone. References & Resources: Microsoft’s Open-Source Journey – Azure Blog https://techcommunity.microsoft.com/t5/linux-and-open-source-blog/linux-and-open-source-on-azure-quarterly-update-february-2025/ba-p/4382722 Cloud Hypervisor Project Rust-VMM Community Microsoft LISA (Linux Integration Services Automation) Repository Cloud-LTS Linux CVE Analysis Project
