Rystad Energy says its AskRystad – Analytics agent is now available through Microsoft 365 Copilot’s Agent Store, putting the company’s subscribed energy-market research inside Copilot experiences used in Excel, PowerPoint and Teams. The practical change is that licensed Rystad customers can ask for analysis in the Microsoft 365 workspace where they are preparing a model, briefing or presentation rather than moving through Rystad’s Client Portal, Cube Browser and export process. The announcement, published by Rystad Energy on August 7, says users install the agent, authenticate with existing Client Portal credentials, and then query its Analytics content through Copilot. Microsoft’s Per Christian Honningsvåg is quoted in the release endorsing the integration, but Microsoft has not issued a separate product announcement or public technical listing with the agent’s permissions, data flows, regional availability or support terms.
For IT departments, this is not a blanket addition of Rystad data to every Copilot tenant. It is a third-party agent that still depends on a Microsoft 365 Copilot entitlement, the organization’s Agent Store policy, administrator approval where required, and an existing Rystad client account with access to the underlying intelligence.

Business professional analyzes energy industry data on a laptop amid digital dashboards, analytics, and cybersecurity icons.The integration moves retrieval into the authoring workflow​

Rystad’s pitch is familiar to anyone who has watched analysts lose half a morning assembling a market update: find the latest research, export tables, reconcile the numbers with a previous deck, then rewrite the result in a format executives can use. Its new agent is designed to bring that retrieval step directly into Microsoft 365 Copilot, where a user can ask a question, refine the result with follow-up prompts and use it as material for a spreadsheet, slide deck or Teams discussion.
The company’s examples are deliberately high-value, time-sensitive requests. It cites questions about the 2026 Venezuelan oil-production outlook, upstream investment drivers over the next 18 months, and routine market questions that otherwise get routed to a small group of internal specialists who know the research tools. Those are the kinds of prompts where a proprietary energy-data provider can offer something Copilot’s general web-grounded responses cannot: licensed sector analysis, a controlled research library and data assembled for commercial decision-making.
Rystad has already positioned AskRystad as an AI research assistant for its Analytics library, rather than as a general-purpose model or autonomous analyst. The Copilot release does not announce new datasets, a new forecasting model or a new Rystad subscription tier. It changes the entry point to material clients already buy.
That distinction matters in procurement discussions. The agent may reduce workflow friction, but it does not replace Rystad licensing, nor does it turn public Microsoft 365 Copilot access into access to proprietary oil, gas, power, renewables, supply-chain and clean-technology research. Rystad’s own instructions say users must sign in with Client Portal credentials, indicating that entitlement to the source content remains with Rystad.

MCP is the important technical claim — with limits​

Rystad says the agent uses Model Context Protocol, or MCP, from the beginning. MCP is an open standard intended to let AI applications connect to external tools and data sources in a structured way; Microsoft’s Copilot Studio documentation describes MCP servers as exposing resources and tools that an agent can use, with the server defining available inputs and outputs.
In plain terms, that means the integration can give Copilot a prescribed route to Rystad’s systems rather than relying on a user to manually copy information from a browser into a prompt. For a data provider, that can improve traceability and maintain a clearer boundary between the customer’s licensed research environment and the documents being produced in Microsoft 365.
It also provides a cleaner extensibility path than the older generation of bespoke Copilot plugins and connectors. Microsoft’s current documentation supports bringing partner-built agents into Microsoft 365 Copilot and the Agent Store, while its broader agent tooling increasingly treats MCP as a standard way to connect knowledge, tools and business systems.
But MCP is a connection mechanism, not an accuracy guarantee. It can make authoritative source material available to an AI assistant; it does not ensure that Copilot will interpret a prompt correctly, select the best source, preserve every qualification in a research note or produce a forecast-free summary. Microsoft’s own Windows documentation warns that AI-generated responses may not reflect the user’s intent and should be reviewed for accuracy.
Rystad’s announcement calls its data “trusted” and says the system will produce answers in seconds. Those are vendor claims, and neither Rystad nor Microsoft has published independent testing showing response accuracy, citation behavior, latency under load, handling of ambiguous asset names, or whether the agent exposes underlying tables and report references alongside its prose. For energy-market work, those details matter more than the speed of the first answer.

Agent Store availability still leaves an admin gate​

Microsoft describes the Agent Store as the place where users can discover and install Microsoft, partner and organization-built agents. However, Microsoft’s administrator guidance is clear that Agent Store availability is governed at the tenant level: administrators can make agents available, assign them to users or groups, block them and remove them.
That creates a likely deployment sequence for a Rystad customer. A user may be able to find AskRystad in the Agent Store only if the organization allows partner agents and has made the relevant agent available; the user then must authenticate against Rystad’s client service. An employee cannot reasonably treat the “now live” wording as proof that the tool will appear in every corporate Copilot sidebar today.
Microsoft’s documentation also says a Microsoft 365 Copilot license is a prerequisite for Agent Store access in the enterprise setup flow. Rystad has not published its own pricing, whether the agent is included with every Analytics subscription, which client tiers are eligible, or whether any agent usage introduces separate costs beyond the customer’s Rystad and Microsoft agreements.
Those omissions are material. Energy companies, consultancies and investors often divide access by geography, commodity coverage, research product and project team. Before broad deployment, administrators will need to determine whether the Rystad identity presented to Copilot respects those existing entitlements consistently—and whether a user can accidentally turn restricted research into a broadly shared Teams message, PowerPoint file or Excel workbook.

The security review is about what leaves each boundary​

The most consequential unknown is not whether AskRystad can retrieve a public market outlook. It is how the agent handles prompts that blend Rystad intelligence with internal deal assumptions, production plans, investment committee questions or customer data.
Microsoft says organizations can review an agent’s publisher, tools, data access, security and compliance information in the Microsoft 365 admin center. Microsoft also states that admins can manage deployment, access and lifecycle controls for partner-built agents. Those controls are useful, but they do not eliminate the need to inspect the specific Rystad agent’s manifest and published privacy terms before enabling it.
Rystad’s release does not disclose whether prompts are stored by Rystad, how long any records are retained, whether prompts and responses are used for service improvement, which data-residency options apply, what logging is available to the customer, or how the integration behaves when a query combines Microsoft 365 content with Rystad material. It also does not state whether the MCP endpoint is read-only or whether future workflow expansion could include actions beyond research retrieval.
The conservative operating model is straightforward: treat AskRystad as a connected external research service, not as an extension of the tenant’s own Microsoft 365 data boundary. Pilot it with a limited group, review the agent’s declared data and tool permissions, verify Rystad subscription entitlements, and test a realistic set of ambiguous, sensitive and high-stakes prompts before enabling self-service access.

Spektra points to a wider Rystad AI strategy​

The Copilot agent arrives while Rystad is preparing the full commercial launch of Spektra, its AI-native market-intelligence platform, on August 20. Rystad announced in June that Spektra includes AskRystad, MCP connectors and an API gateway, following a beta program involving 78 client companies.
That context makes the Microsoft 365 agent more than a standalone Office add-on. Rystad is building several routes into the same research estate: its own platform, its conversational assistant, APIs and now a Copilot-facing agent. For existing clients, that could reduce the pressure to standardize every analyst workflow on one Rystad interface. For Rystad, it places its data where the written record of a decision is created.
The risk is that convenience can flatten the distinction between a quick conversational answer and the underlying analysis needed to defend an investment, procurement or strategy decision. The organization that gets the most value from this agent will be the one that uses it to accelerate first drafts and routine research while preserving an audit trail back to the relevant Rystad report, dataset, analyst assumptions and timestamp.
Rystad has made AskRystad easier to reach. The next operational task for customers is to decide who can reach it, what information they can send to it, and how much verification is required before its Copilot-generated wording becomes part of a decision document.

References​

  1. Primary source: Rystad Energy
    Published: August 7, 2026 at 12:00 AM UTC
  2. Related coverage: learn.microsoft.com
  3. Related coverage: learn.microsoft.com
  4. Related coverage: globenewswire.com
  5. Related coverage: rystadenergy.com
  6. Related coverage: techcommunity.microsoft.com
  7. Related coverage: devblogs.microsoft.com
  8. Related coverage: adoption.microsoft.com