Microsoft Copilot - Anymorph

Background: provider and product surface

Microsoft Copilot is a family of assistant surfaces across Bing, Edge, Windows, M365, GitHub, and Microsoft Graph. Public web visibility and enterprise knowledge visibility should be measured separately.

Usage scale and market context

Metric	Reported value	Context
MAU/WAU	Not consistently disclosed as one unified Copilot number	Microsoft reports across Bing, Windows, GitHub, and M365 surfaces separately
Enterprise distribution	M365 seat base / organizational rollout	Depends on tenant adoption, permissions, and Graph data quality
Product context	Product family, not one app	Public web Copilot and M365 Copilot should be separated

Product surface and user experience

Public Copilot/Bing-like answers and M365 Copilot are different surfaces.
M365 can use emails, docs, meetings, Teams, files, and connector data.
Citation pills, inline citations, and side panes vary by product.
In enterprise, internal knowledge hygiene can matter more than public SEO.

GEO characteristics

Axis	Engine-specific behavior	GEO interpretation
Retrieval substrate	Bing + Microsoft Graph/M365 + connectors	Separate public web and enterprise knowledge
Citation UI	Citation pills, inline citations, side-pane sources	Source UI varies by product surface
Query/context	Utterance + selected document/email/thread context	Permissions and Graph context change answers
Enterprise personalization	Tenant adoption, permissions, Graph quality	Organization-level setup matters
Measurement note	Separate Bing-visible sources from internal sources	External SEO and internal knowledge hygiene are different problems

Key cited / influential source types

Source type	Observed pattern	GEO action
Bing-visible web pages	Public Copilot candidate pool	Manage Bing SEO, canonical, and indexation
Microsoft docs / GitHub	Strong ecosystem sources for developer/B2B prompts	Strengthen GitHub/docs/LinkedIn source graph
LinkedIn/company profiles	Microsoft ecosystem entity signal	Maintain B2B identity signals
SharePoint/Teams/Outlook docs	M365 internal sources	Manage owner/date/permissions/source of truth
Structured specs/tables/FAQs	Enterprise answer extraction surfaces	Structure product/process/pricing/policy docs

Engine-specific GEO strategy

Strategy	Action	Metric
Separate public vs enterprise	Use different KPIs for Bing web and M365 Graph answers	Surface-specific source
Improve internal AI-readability	Clean owner/date/table/FAQ/permissions	Internal citation quality
Strengthen Microsoft ecosystem sources	Manage LinkedIn, GitHub, Microsoft partner/docs presence	Ecosystem mention
Maintain connector hygiene	Improve Salesforce/Jira/S3 connector data quality	Connector-grounded answer accuracy

What to measure

Usage scale and surface-specific exposure
Source/citation presence and source type
Brand mention, recommendation, sentiment, and claim accuracy
Engine-specific failure mode: retrieval, citation, or recommendation

Sources

VisibilityTrack brand presence, share, sentiment, competitors, and top citations