Login
Enhancing Power Pages Experience with Copilot Hub
Artificial Intelligence is rapidly becoming the backbone of modern web experiences. Microsoft Power Pages has embraced this shift by weaving AI-powered features deeply into both the site-building and the end-user journey from intelligent chatbots and smart search summaries to AI-assisted form filling and data summarization.
But with great power comes the need for great governance. How do administrators ensure that these AI features are used responsibly across multiple environments? How do they track which features are being adopted, and by how many users? Enter the Copilot Hub for Power Pages, a centralized command center inside the Power Platform Admin Center designed to give admins full visibility and control over AI capabilities.
In this blog, we will walk through the Copilot Hub in detail, what it offers, why it matters, real-world use cases, and a step-by-step guide for admins to get started.
Key Takeaways
- Gain centralized visibility into AI feature adoption across all Power Pages environments.
- Monitor both maker and end-user Copilot usage through built-in analytics and insights.
- Control AI-powered capabilities at the environment or site level with granular governance settings.
- Support compliance and security requirements by selectively enabling or restricting AI features.
- Provide a seamless experience for users through automatic fallback to standard functionality when AI features are disabled.
What is the Copilot Hub for Power Pages?
The Copilot Hub is a dedicated section within the Power Platform Admin Center that provides a unified dashboard for tenant administrators to monitor, analyse, and govern the usage of AI-powered features across all Power Pages environments in their tenant.
In simple terms, it answers three critical admin questions:
- Who is using AI features, and how often?
- Which AI features are enabled or disabled across my environments?
- How do I control AI feature access for makers and end users at a granular level?
The Copilot Hub is split into two primary capabilities:
- Analytics & Insights
- Governance Controls for AI Features
Real- World Use Cases
Before diving into the how-to, let us look at scenarios where the Copilot Hub solves real business problems.
Use Case 1: Financial Services – Compliance-Driven AI Governance
A bank uses Power Pages for a loan application portal. Due to compliance regulations, they cannot allow AI to auto-fill sensitive form fields on certain forms. The admin uses the Copilot Hub’s granular site-level controls to disable AI Form Fill Assistance on specific loan application sites, while keeping it enabled on informational sites. This gives them the compliance control they need without disabling AI globally.
Use Case 2: Large Enterprise – Cross-Department AI Adoption Tracking
A large manufacturing company has 50+ Power Pages sites used across HR, Legal, Procurement, and Customer Support departments. The Power Platform CoE (Center of Excellence) team wants to understand which departments are actively adopting Copilot features. Using the Maker Copilot and End-User Copilot analytics in the Copilot Hub, they can track Monthly Active Users (MAU) per site, identify low-adoption areas, and create targeted training programs.
How to Access Copilot Hub for Power Pages
Follow these steps to access the Copilot Hub in the Power Platform Admin Center:
- Step 1: Go to the Power Platform Admin Center at https://admin.powerplatform.microsoft.com/
- Step 2: In the left-hand navigation panel, look for and click on ‘Copilot Hub’.
- Step 3: On the Copilot Hub page, click on the ‘Power Pages’ tab to access product-specific insights and settings.
Analytics & Insights
The Analytics section of the Copilot Hub gives tenant admins a detailed picture of how AI features are being consumed, both by makers building the sites and by end users interacting with the published portals. Admins can toggle between two views:
- Maker Copilot Analytics
- End-User Copilot Analytics
Maker Copilot Analytics
This view provides insights into how site builders (makers and pro developers) use AI features during the site creation process. It covers Studio Copilot (used in the Power Pages Design Studio) and Prodev Copilot (used via the VS Code extension).
Key Metrics Available:
| Metric | Description |
| Studio Copilot MAU | Monthly active makers using AI features in the design studio |
| Prodev Copilot MAU | Monthly active pro developers receiving AI-generated responses |
| Sites with Copilot Enabled | Number of sites where Copilot features are turned on |
| Copilot Usage Trend | Time-based chart showing Copilot usage over a selected period |
| Most Used Copilot Features | Insights into which AI capabilities are most frequently used by makers |
End-User Copilot Analytics
This view focuses on how actual site visitors and end users interact with AI-powered features embedded in published Power Pages portals. It provides feature-level metrics for each AI capability.
Features tracked and their metrics:
| Feature | Key Metrics |
| Chat Agent / Add an Agent | Total Sites Enabled, MAU, Usage Trend, Site details table |
| Search Summary | MAU, Total Sites Enabled, Search Query Volume, Usage Table |
| Summarization API | API Usage Volume, Total Sites Enabled, Usage Table |
| AI Form Fill Assistance | MAU, Total Sites Enabled, Fields Auto-Filled, Form Submission Rate |
| AI Summary List | MAU, Total Sites Enabled, Site-level breakdown table |
Governance Controls for AI Features
The Governance Controls section is where admins exercise full authority over which AI features are available, to whom, and in which environments or sites. This is the most powerful aspect of the Copilot Hub.
Admins can:
- Enable or disable AI features for makers (Studio Copilot, Prodev Copilot)
- Enable or disable AI features for end users (chatbot, search summary, form fill, etc.)
- Apply controls at the environment level or at the individual site level
Step-by-Step: Configuring AI Feature Governance
- Step 1: In the Copilot Hub, click on the ‘Settings’ link next to the Power Pages tab.
- Step 2: Use the product filter dropdown and select ‘Power Pages’.
- Step 3: You will see a list of all available AI features for Power Pages. Click on any feature (e.g., ‘AI Form Fill Assistance’) to configure it.
- Step 4: A list of all environments in your tenant is displayed, showing Environment Name, Type, Region, and current Status (On/Off).
- Step 5: Select the environment you want to configure and click ‘Set up / Edit’.
- Step 6: Choose the appropriate enablement scope:
| Option | Description |
| On – All Sites | Enables AI-powered experiences for ALL websites in the environment |
| All Sites Except Specific Sites | Enables for all sites except selected ones. Overrides maker configurations. |
| Specific Sites Only | Enables AI only on selected sites. Prevents access elsewhere. |
| None of the Sites | Disables ALL AI-powered experiences across the environment. Overrides makers. |
- Step 7: Click ‘Save’ to apply the settings.
Important Considerations & Dependencies
When managing AI features in the Copilot Hub, keep the following in mind:
- Tenant-level PowerShell controls (enableGenerativeAIFeaturesForSiteUsers) take precedence. If AI is disabled at tenant level, environment-level settings cannot be configured from the Copilot Hub.
- Only tenant-level admins (Power Platform Administrator or Dynamics 365 Administrator AAD roles) can modify governance settings. Environment-level users cannot access or modify these settings.
- For the Chat Agent feature: If ‘Publish bots with AI’ is disabled at the tenant level, the site Copilot cannot be configured in the Copilot Hub.
- If Bing Search is disabled at the environment level, all Copilot features that depend on Bing search will be unavailable.
- The ‘Move data across regions’ setting at the environment level affects whether Copilot can operate when Azure OpenAI capacity in the local region is insufficient.
Maker Experience When AI Features Are Disabled
When a tenant admin disables AI features, makers building sites in the Design Studio will immediately see the impact:
- If a Maker Copilot feature (Studio or Prodev Copilot) is disabled, makers see an in-product message informing them the feature has been turned off by an admin, with a prompt to reach out to their administrator.
- If End-User AI features (chatbot, search summary, form fill) are disabled, the configuration options for those features in the Design Studio appear greyed out with a message indicating they are managed by the admin.
End-User Experience When AI is Blocked
When generative AI features are turned off for a site’s end users, the experience gracefully falls back to the standard non-AI version. For example:
- Users see a standard keyword-based search instead of an AI-powered search summary.
- Form fields appear as regular fields — no AI auto-fill from document upload.
- No chatbot is presented if the Chat Agent has been disabled.
Importantly, users do not see any messaging about organizational policies or governance controls — the fallback is seamless
Conclusion
The Copilot Hub for Power Pages is a powerful, much-needed addition to the Power Platform Admin Centre. As AI features become mainstream in Power Pages portals — from intelligent chatbots to AI-assisted form filling — the ability to monitor, analyse, and govern these capabilities at scale becomes critical for enterprise IT and compliance teams.
To summarize what the Copilot Hub offers:
- Centralized analytics for both Maker and End-User Copilot features
- Feature-level governance at both environment and site granularity
- Transparent feedback to makers when features are restricted
- Seamless fallback for end users when AI is disabled
Whether you are an IT admin rolling out Power Pages across a large enterprise, a compliance officer in a regulated industry, or a Power Platform CoE lead tracking AI adoption — the Copilot Hub gives you the visibility and control you need.
The post Enhancing Power Pages Experience with Copilot Hub first appeared on Microsoft Dynamics 365 CRM Tips and Tricks.
