TestingOps.ai

MCP tools for agents · MCP tool for agents

Microsoft Learn and TestingOps: Microsoft documentation for test agents

Connect the Microsoft Learn MCP server and TestingOps agents can check Microsoft's own documentation when the application under test runs on Azure, Dynamics 365, Power Platform or .NET.

  • MCP tool for agents
  • Available
Request a demo Microsoft Learn MCP server
Connection
MCP tool for agents
Writes back
Nothing, its tools only read
Last checked
7 Nov 2026

In short

Microsoft Learn and TestingOps in short

The Microsoft Learn connection is an MCP tool that lets TestingOps agents search Microsoft's public documentation, fetch complete articles and search code samples, with no key and no Microsoft account.

Agents can use it to check how a Dynamics 365 form, a Power Apps control or an Azure service is documented to behave, before they write a case or call a failure a defect.

It only returns public documentation, so TestingOps opens its tools on connect without an approval step.

What it does

What it does for your testing

  1. 1

    Documented behaviour of platform features

    Input
    A Dynamics 365, Power Platform or Azure feature the app relies on
    TestingOps
    Agents can search Microsoft Learn for the feature's documented behaviour and limits
    Output
    Expected results that match Microsoft's documentation
  2. 2

    Error codes explained

    Input
    An Azure or .NET error a run returned
    TestingOps
    Agents can look up the error in Microsoft's documentation
    Output
    An explanation and a likely cause for the analysis

Step by step

How it works

  1. Pick Microsoft LearnUnder Integrations → API & MCP, pick Microsoft Learn in Extra tools your agents may use.
  2. Connect without a keySelect Connect. The tools are open to your agents right away; documentation servers get no approval step.
  3. Agents search when they need itDuring a task, an agent can search Microsoft's documentation or code samples and fetch a full article.

This is not the Microsoft Teams and Copilot guide. That guide is about using TestingOps from Microsoft's apps; this tool gives TestingOps agents Microsoft's documentation.

Connect

Setup

  1. In TestingOps, as customer admin, open Integrations → API & MCP and pick Microsoft Learn under Extra tools your agents may use (outgoing, over MCP).
  2. Select Connect.

Documentation: Microsoft Learn MCP server

Where you connect it in TestingOps: Integrations → API & MCP → Extra tools your agents may use → Microsoft Learn

Use cases

Use cases

Test a customised Dynamics 365 process

Trigger
Cases cover a customised Dynamics 365 sales process
Uses
Microsoft's documentation for the standard process and its settings
Agent activity
Can check which behaviour is standard and which comes from your customisation
Result
Cases that separate platform behaviour from your changes

Explain an Azure error in a run

Trigger
An API step fails with an Azure error code
Uses
Azure documentation for that service
Agent activity
Can look up the error and its usual causes
Result
An analysis that names the likely cause, such as a quota or configuration limit

Check a Power Apps control

Trigger
A canvas app control behaves unexpectedly in a case
Uses
Power Apps documentation
Agent activity
Can read how the control is documented to behave
Result
A clear call on whether the app or the case needs fixing

Capabilities

Capabilities and limits

What is read

Microsoft's public documentation and code samples on Microsoft Learn

What is produced

Documentation context for agents' test design and analysis; nothing is stored in TestingOps by the tool itself

Where it can write

Nothing. The server only returns documentation.

How it connects

The Microsoft Learn MCP server (https://learn.microsoft.com/api/mcp), without authentication

Account and permissions

  • No Microsoft account or key
  • Customer admin (or Manage integrations) rights in TestingOps; the tool is visible only to agents working on your organisation's projects

Limits

  • Public documentation only; your own tenant's settings and data are not visible to it
  • Microsoft refreshes the content incrementally and fully once a day, so the newest changes can take a while to appear
  • Agents running on Grok receive no MCP tools

Example

Example: how a team uses it

Illustrative scenario, not a customer story.

A team tests a Power Apps canvas app with a gallery over a large table. A case expects all 3,000 records to appear, but only 500 do. The agent can look up the delegation documentation on Microsoft Learn and finds the documented row limit for queries that cannot be delegated.

Its analysis points to the app's query design rather than a platform defect, with a reference to the documentation section.

Frequently asked questions

Does it see our Azure subscription or tenant?

No. It searches Microsoft's public documentation; your tenant's configuration and data are not part of it.

Is there a cost or a key?

Microsoft offers the server publicly without authentication and without charge, and TestingOps connects without a key.

Is this the Teams or Copilot integration?

No. Using TestingOps from Microsoft Teams or Microsoft 365 Copilot is a separate connection guide. This tool only gives agents Microsoft's documentation.

Does it need approval?

No. It only returns documentation, so TestingOps opens its tools on connect without an approval step.

Next step

Request a demo to see agents use Microsoft's documentation while they test a Microsoft-based application.

Request a demoMore mcp tools integrations