Microsoft Discovery

Agentic research platform that orchestrates specialized agents over a knowledge graph and high performance computing.

Provider: azure
Kind: AI service
Category: Compute
Official docs: https://learn.microsoft.com/en-us/azure/microsoft-discovery/overview-what-is-microsoft-discovery

Properties · 2 set by this component

property	type	values	required	kind default	this component
auth	enum	api-key \| oauth \| iam \| none	no	—	▸ iam
contentFiltering	boolean	—	no	—	inherited
customerManagedKeys	boolean	—	no	—	inherited
dataResidency · advanced	enum	us \| eu \| asia \| global	no	—	inherited
dataRetentionDays	integer	—	no	—	inherited
experience · component property	enum	cloud-service \| desktop-app	no	—	inherited
governanceControls · component property	boolean	—	no	true	inherited
hpcIntegration · component property	boolean	—	no	true	inherited
keyStore	boolean	—	no	false	inherited
knowledgeGraph · component property	boolean	—	no	true	inherited
managed	boolean	—	no	false	▸ true
modality	enum	text \| vision \| speech \| multimodal \| structured \| image \| video \| audio \| embedding \| rerank	no	—	inherited
publicEndpoint	boolean	—	no	—	inherited
quotaUnitsPerMinute	integer	—	no	—	inherited
rateLimitRpm · advanced	integer	—	no	—	inherited
rateLimitTpm · advanced	integer	—	no	—	inherited
viaGateway	boolean	—	no	false	inherited

Rules that apply · 2

Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.

AI API key not managedwarning

ai-api-key-unmanaged

This AI vendor is reached with an API key, and nothing in the design holds or rotates that key. It ends up in environment files or code, every caller shares it, and a single leak runs up the vendor bill until someone notices. Put the key in a key-management component, or say it is held there with keyStore.

— all of these hold:
— the node's `auth` is "api-key"
— the node's `keyStore` is false
— the node has at least one incoming edge from an app-server, worker or client
— this does not hold:
— the design contains a node of kind key-management

Stateful node without zone redundancyerror

stateful-node-without-zone-redundancy

A stateful compute node pinned to exactly one availability zone disappears with that zone, and its state goes with it. Nodes inside a cell are exempt, because there the cell is deliberately single-zone and redundancy comes from the other cells.

— all of these hold:
— the node's `stateless` is false
— the node sits inside exactly 1 availability-zone group
— this does not hold:
— the node sits inside at least one cell group

Use it in a design

nodes:
  - { id: "discovery", component: "azure-discovery" }

Other AI service products · 125

and 85 more → AI service page

Source

1# yaml-language-server: $schema=../../schema/component.schema.json
2# Microsoft Discovery: an agentic research platform built on Azure that combines agent orchestration,
3# reasoning, a graph-based knowledge foundation and high performance computing ("What is Microsoft
4# Discovery?"). That page states the Discovery Engine stores its outcomes in a long-term memory knowledge
5# graph, that agents run in-silico experiments on HPC clusters, that built-in governance controls provide
6# central management and audit trails, and that the product ships as an enterprise cloud service and a
7# desktop app. Microsoft Discovery is in public preview.
8schemaVersion: "1"
9type: "component"
10id: "azure-discovery"
11kind: "ai-service"
12provider: "azure"
13docs: "https://learn.microsoft.com/en-us/azure/microsoft-discovery/overview-what-is-microsoft-discovery"
14defaults:
15  auth: "iam"
16  managed: true
17properties:
18  experience:
19    type: "enum"
20    values: ["cloud-service", "desktop-app"]
21  knowledgeGraph:
22    type: "boolean"
23    default: true
24  hpcIntegration:
25    type: "boolean"
26    default: true
27  governanceControls:
28    type: "boolean"
29    default: true

The same page as markdown, for an agent: /catalogue/components/azure-discovery.md