Copilot spans more surfaces than any other AI assistant, but every surface that grounds in the open web shares one retrieval backbone - the Bing index - even when the generation model varies.
Bing index (retrieval). Microsoft's web index is the retrieval substrate for every Copilot surface that grounds in the open web. When Copilot needs current information, it turns the user's prompt into a query, sends it to Bing, and grounds its answer in what comes back - so the pages it can cite are exactly the pages Bing has indexed. Microsoft's own support documentation describes this Bing grounding step on both the consumer and the Microsoft 365 surfaces. For GEO, this makes Bing indexation the hard prerequisite: a page Bing has not indexed cannot be retrieved, and therefore cannot be cited, anywhere in Copilot.
Generation models. Copilot writes its answers with a mix of models, chosen by surface, tier, and task. The core has long been OpenAI's GPT family, supplied through the Microsoft-OpenAI partnership, which was renewed in April 2026 as a non-exclusive license running through 2032. Microsoft now pairs that with its own in-house MAI (Microsoft AI) models, and has broadened the lineup further inside Copilot Studio. The model that does the writing shapes tone and synthesis, but not which pages get cited - that is decided upstream, in retrieval and reranking - so for GEO the generation layer is the part you do not optimize against.
Prometheus. Prometheus is Microsoft's orchestration layer, the system that sits between the user's prompt and the language model. Its Bing Orchestrator expands a single prompt into multiple Bing queries, runs them, and assembles fresh, relevant results into the context the model reasons over, then attaches citations to the sources it used. It is the machinery that turns Bing retrieval into a grounded, cited Copilot answer rather than an ungrounded guess. For GEO, Prometheus is where the real contest happens: a page earns a citation by being one of the results it pulls forward and grounds the answer in, which rewards clean structure, clear direct answers, and freshness.
Microsoft 365 surfaces. Microsoft 365 Copilot lives inside Word, Excel, PowerPoint, Outlook, and Teams, and it is a separate enterprise surface with its own grounding. Its first source is the Microsoft Graph - the user's own work data, including email, documents, calendar, chats, and meetings - accessed strictly within that user's existing permissions. When a prompt needs outside context, it adds Bing-grounded web retrieval on top, the same web layer the consumer surfaces use. For GEO, only that web-grounded portion is reachable from the outside: the Graph half is private tenant data, but the public-web half still answers from Bing, so the same Bing indexation and structure work carries into this enterprise surface.
Edge / Windows / Bing.com. These are Copilot's consumer distribution surfaces: the Edge sidebar, the Windows taskbar, Bing.com chat, and the standalone copilot.microsoft.com app. They put the assistant in front of hundreds of millions of everyday users without anyone needing to seek it out, and they all answer from the same Bing-grounded retrieval pool that the enterprise web layer uses. The packaging differs by surface, but the cited sources are drawn from the one index. For GEO, that consolidation is the opportunity: a single page that ranks well in Bing is eligible to be cited across all of these consumer entry points at once.
