Microsoft.Discovery Supercomputer deployment fails with InvalidResourceType

Dimitri Obolensky 0 Reputation points Microsoft Employee
2026-07-04T08:57:14.7866667+00:00

Title: Microsoft.Discovery Supercomputer deployment fails with InvalidResourceType although provider metadata and ARM validation recognize the resource type

Summary

I am attempting to deploy a Microsoft Discovery Supercomputer (Microsoft.Discovery/supercomputers) into subscription 9c69fc18-81c6-4464-8dcc-e0e681724e79.
I have tried to deploy through the Azure portal and through ARM templates and get the same error.

The deployment consistently fails with:

{

"code": "InvalidResourceType",

"message": "The resource type could not be found in namespace 'Microsoft.Discovery' for api version '<api-version>'."

}

However:

  1. The Microsoft.Discovery provider is registered.
  2. The provider metadata advertises supercomputers as a supported resource type.
  3. ARM template validation succeeds.
  4. The failure occurs for all advertised API versions.
  5. Direct REST calls to the RP also fail with the same error.

This suggests an inconsistency between the Discovery RP metadata and the backend implementation/availability of the supercomputers resource type.

Subscription

SubscriptionId: 9c69fc18-81c6-4464-8dcc-e0e681724e79

Resource Group: Discovery

Region: East US

Resource Name: sc-discovery

Provider Registration

Namespace: Microsoft.Discovery

RegistrationState: Registered

Provider metadata advertises:

Resource Type: supercomputers

Supported API Versions:

  • 2026-06-01
  • 2026-02-01-preview

ARM Template Validation

The following command succeeds:

az deployment group validate `` --resource-group Discovery `` --template-file templatedisco.json

Validation output includes:

Provider: Microsoft.Discovery

Resource Type: supercomputers

Resource:

/subscriptions/9c69fc18-81c6-4464-8dcc-e0e681724e79/

resourceGroups/Discovery/

providers/Microsoft.Discovery/

supercomputers/sc-discovery

Validation state:

ProvisioningState: Succeeded

Deployment Failure

Command:

az deployment group create `` --resource-group Discovery `` --template-file templatedisco.json --name deploy-sc-discovery

Deployment operation returns:

{ "statusCode": "NotFound", "code": "InvalidResourceType", "message": "The resource type could not be found in namespace 'Microsoft.Discovery' for api version '2026-06-01'." }

Tracking ID:05d5f6b3-6b5a-443e-9463-753c4bc36a07

I also tested:

2026-02-01-preview

2026-06-01

All return the same error.

Direct RP REST Test

Query:

GET /subscriptions/9c69fc18-81c6-4464-8dcc-e0e681724e79/providers/Microsoft.Discovery/supercomputers?api-version=2026-06-01

Result:

{ "error": { "code": "InvalidResourceType", "message": "The resource type could not be found in namespace 'Microsoft.Discovery' for api version '2026-06-01'." }}

The same occurs for:

2026-02-01-preview

Current Assessment

The evidence appears to indicate:

  • ARM recognizes Microsoft.Discovery/supercomputers.
  • Provider metadata advertises the resource type and API versions.
  • ARM template validation succeeds.
  • Direct RP calls against /supercomputers fail with InvalidResourceType.
  • The issue is therefore unlikely to be caused by the ARM template itself.
  • It appears that the Discovery RP metadata and the RP backend implementation/availability are out of sync, or that an additional RP-side flight/feature flag is required for this subscription.

Request

Could the Discovery RP team please verify:

  1. Whether Microsoft.Discovery/supercomputers is expected to be available in subscription 9c69fc18-81c6-4464-8dcc-e0e681724e79.
  2. Whether additional onboarding/feature flighting is required.
  3. Whether the supercomputers route is properly enabled for:
    • 2025-07-01-preview
      • 2026-02-01-preview
        • 2026-06-01
        1. Whether tracking ID 05d5f6b3-6b5a-443e-9463-753c4bc36a07 reveals a backend RP failure.

Thank you.Title: Microsoft.Discovery Supercomputer deployment fails with InvalidResourceType although provider metadata and ARM validation recognize the resource type

Summary

I am attempting to deploy a Microsoft Discovery Supercomputer (Microsoft.Discovery/supercomputers) into subscription 9c69fc18-81c6-4464-8dcc-e0e681724e79.

The deployment consistently fails with:

{

"code": "InvalidResourceType",

"message": "The resource type could not be found in namespace 'Microsoft.Discovery' for api version '<api-version>'."

}

However:

  1. The Microsoft.Discovery provider is registered.
  2. The provider metadata advertises supercomputers as a supported resource type.
  3. ARM template validation succeeds.
  4. The failure occurs for all advertised API versions.
  5. Direct REST calls to the RP also fail with the same error.

This suggests an inconsistency between the Discovery RP metadata and the backend implementation/availability of the supercomputers resource type.

Subscription

SubscriptionId: 9c69fc18-81c6-4464-8dcc-e0e681724e79

Resource Group: Discovery

Region: East US

Resource Name: sc-discovery

Provider Registration

Namespace: Microsoft.Discovery

RegistrationState: Registered

Provider metadata advertises:

Resource Type: supercomputers

Supported API Versions:

  • 2026-06-01
  • 2026-02-01-preview
  • 2025-07-01-preview

ARM Template Validation

The following command succeeds:

az deployment group validate </span><br></div><div><span attribution="{&quot;name&quot;:&quot;Copilot&quot;,&quot;oid&quot;:&quot;E64C3D4F-5E12-4514-AD9B-893A6FAFD00C&quot;,&quot;id&quot;:&quot;E64C3D4F-5E12-4514-AD9B-893A6FAFD00C&quot;,&quot;userInfo&quot;:{&quot;name&quot;:&quot;Copilot&quot;,&quot;oid&quot;:&quot;E64C3D4F-5E12-4514-AD9B-893A6FAFD00C&quot;,&quot;id&quot;:&quot;E64C3D4F-5E12-4514-AD9B-893A6FAFD00C&quot;},&quot;timestamp&quot;:1783154700000,&quot;dataSource&quot;:0}"> --resource-group Discovery

--template-file templatedisco.json

Validation output includes:

Provider: Microsoft.Discovery

Resource Type: supercomputers

Resource:

/subscriptions/9c69fc18-81c6-4464-8dcc-e0e681724e79/

resourceGroups/Discovery/

providers/Microsoft.Discovery/

supercomputers/sc-discovery

Validation state:

ProvisioningState: Succeeded

Deployment Failure

Command:

az deployment group create </span><br></div><div><span attribution="{&quot;name&quot;:&quot;Copilot&quot;,&quot;oid&quot;:&quot;E64C3D4F-5E12-4514-AD9B-893A6FAFD00C&quot;,&quot;id&quot;:&quot;E64C3D4F-5E12-4514-AD9B-893A6FAFD00C&quot;,&quot;userInfo&quot;:{&quot;name&quot;:&quot;Copilot&quot;,&quot;oid&quot;:&quot;E64C3D4F-5E12-4514-AD9B-893A6FAFD00C&quot;,&quot;id&quot;:&quot;E64C3D4F-5E12-4514-AD9B-893A6FAFD00C&quot;},&quot;timestamp&quot;:1783154700000,&quot;dataSource&quot;:0}"> --resource-group Discovery

--template-file templatedisco.json `

--name deploy-sc-discovery

Deployment operation returns:

{

"statusCode": "NotFound",

"code": "InvalidResourceType",

"message": "The resource type could not be found in namespace 'Microsoft.Discovery' for api version '2026-06-01'."

}

Tracking ID:

05d5f6b3-6b5a-443e-9463-753c4bc36a07

I also tested:

2025-07-01-preview

2026-02-01-preview

2026-06-01

All return the same error.

Direct RP REST Test

Query:

GET

/subscriptions/9c69fc18-81c6-4464-8dcc-e0e681724e79/

providers/Microsoft.Discovery/supercomputers

?api-version=2026-06-01

Result:

{

"error": {

"code": "InvalidResourceType",

"message": "The resource type could not be found in namespace 'Microsoft.Discovery' for api version '2026-06-01'."

}

}

The same occurs for:

2025-07-01-preview

2026-02-01-preview

Current Assessment

The evidence appears to indicate:

  • ARM recognizes Microsoft.Discovery/supercomputers.
  • Provider metadata advertises the resource type and API versions.
  • ARM template validation succeeds.
  • Direct RP calls against /supercomputers fail with InvalidResourceType.
  • The issue is therefore unlikely to be caused by the ARM template itself.
  • It appears that the Discovery RP metadata and the RP backend implementation/availability are out of sync, or that an additional RP-side flight/feature flag is required for this subscription.

Request

Could the Discovery RP team please verify:

  1. Whether Microsoft.Discovery/supercomputers is expected to be available in subscription 9c69fc18-81c6-4464-8dcc-e0e681724e79.
  2. Whether additional onboarding/feature flighting is required.
  3. Whether the supercomputers route is properly enabled for:
    • 2025-07-01-preview
    • 2026-02-01-preview
    • 2026-06-01
    1. Whether tracking ID 05d5f6b3-6b5a-443e-9463-753c4bc36a07 reveals a backend RP failure.

Thank you.

StorSimple
StorSimple

A Microsoft hybrid cloud storage solution that combines on premise hardware storage and cloud storage.

0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.