<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Copilot on Pavel Nasovich's Blog</title><link>https://forcewake.me/tags/copilot/</link><description>Recent content in Copilot on Pavel Nasovich's Blog</description><generator>Hugo -- 0.157.0</generator><language>en-us</language><copyright>Copyright 2026</copyright><lastBuildDate>Tue, 08 Jul 2025 15:20:03 +0200</lastBuildDate><atom:link href="https://forcewake.me/tags/copilot/index.xml" rel="self" type="application/rss+xml"/><item><title>GitHub Copilot Agent Mode: EU Data Residency &amp; AI Act Compliance Checklist</title><link>https://forcewake.me/github-copilot-agent-mode-eu-data-residency-ai-act-compliance-checklist/</link><pubDate>Tue, 08 Jul 2025 00:00:00 +0000</pubDate><guid>https://forcewake.me/github-copilot-agent-mode-eu-data-residency-ai-act-compliance-checklist/</guid><description>GitHub Copilot’s new Agent mode executes its language-model inference on Azure OpenAI GPUs that sit wholly inside Microsoft’s EU Data Boundary—provided your tenant is in the EU/EFTA and the “cross-region capacity” switch stays off*. Prompts, repo context and outputs never leave the EU at rest, though limited pseudonymised telemetry can flow to Microsoft’s global SOC. Under the EU AI Act, Copilot is a general-purpose AI (GPAI) service; Microsoft/GitHub must supply risk management, transparency notes and system cards, while *you* must keep logs, run a DPIA and enforce human review. Deadlines: GPAI obligations bite 2 Aug 2025. A five-step checklist below locks your setup to the EU and aligns you with the Act.</description></item></channel></rss>