My IT department only allows Copilot. Now what?

Here is a conversation we hear constantly: "This looks great, but my company standardized on Copilot. IT and Compliance will never approve another AI tool."

Good news. If your company runs Copilot, most of the hard work of approving Virgil already happened. You just have to know what to ask for.

First, what Copilot actually is

"We have Copilot" usually means one of two things.

Microsoft 365 Copilot lives inside Word, Excel, Outlook, and Teams. It is genuinely useful inside each app, and it is sealed inside each app. It cannot do work that spans your email, your files, your calendar, and your documents at once, because it does not live above the apps. It lives inside them.

GitHub Copilot is the coding assistant your developers use. You probably never touch it, but it matters to this story, as you will see in a minute.

Neither one is a workspace where an assistant does multi-step work across your real files. That gap is what Virgil Terminal fills, and it is not a rip-and-replace pitch. Copilot keeps doing what it does inside Office. Virgil is the layer that works across everything.

The part your IT department will like

Virgil Terminal is BYOK: Bring Your Own Key. Your company's AI keys plug into it, and they stay on your computer. Virgil never proxies your traffic, never sees your prompts, and never becomes a new place your data lives.

That one design choice changes the compliance conversation completely. When IT evaluates a typical AI tool, they are evaluating a new data processor: security review, data agreements, vendor onboarding, months of meetings. With Virgil there is no new data processor. Your prompts travel on your company's existing agreements with Microsoft, Anthropic, or OpenAI, exactly as they already do. The only new vendor is a desktop app.

The keys already exist

This is the part almost nobody has noticed.

In June 2026, GitHub made Copilot itself BYOK for business customers. Companies can now connect their own Anthropic, OpenAI, Azure, and xAI keys to Copilot instead of using GitHub's bundled models. Which means something quietly remarkable: Copilot companies now hold raw AI provider keys, under IT governance, with rotation policies and spend alerts and an owner.

The hardest step of onboarding, getting an approved key, was done for you. By Microsoft.

And if your company is a pure Microsoft shop with no GitHub in sight, there is an equivalent path: Azure OpenAI. If your company has an Azure subscription, IT can issue an Azure OpenAI key where the models run inside your company's own tenant and data boundary, private to your organization, never used for training. Virgil Terminal supports Azure OpenAI directly. This is the IT-blessed route, and IT teams grant it for internal tools all the time.

The actual ask

So the conversation with IT is not "please approve a new AI vendor." It is one sentence:

"Can you issue me a key like the one you already gave Copilot?"

Same provider, same account, same governance, same spend pool, better audit trail if they mint a separate key per app, which many will. Paste it into Virgil's settings and you are running in five minutes, and nothing new touches your company's data.

Keeping it honest

Two caveats, because your IT team will appreciate precision. Copilot's BYOK is a public preview for business plans, so not every company has it switched on yet. And some IT departments will reasonably prefer the Azure OpenAI route, where everything stays inside the company tenant. Both roads lead to the same place: your keys, your data boundary, one flat $49 workspace on top.

Corporate bureaucracy is usually the reason you cannot have nice things. This time, the bureaucracy already did the paperwork. Go ask for your key.