Healthcare Agent Service Deployment Failure

Question

Healthcare Agent Service Deployment Failure

Suma Nalluri 40

I am trying to create a Healthcare Agent Service resource in Azure, but the deployment fails every time during provisioning.

Subscription: POC

Resource Group: rg-care-ai-dev-us

Region: East US

Plan: C1

Resource Name: hcas-tcare-callintake-dev-eus

Provider: Microsoft.HealthBot

Error:

ResourceDeploymentFailure

Message:

The resource write operation failed to complete successfully because it reached terminal provisioning state 'Failed'.

I already tried the following:

Deleted the failed deployment and retried
Tried different resource names
Used the correct lowercase naming format
Checked that the name does not start or end with a hyphen
Retried the deployment multiple times

The issue still continues. Please help identify the underlying provisioning error and confirm whether this is related to HealthBot quota, provider registration, region availability, subscription policy, or backend provisioning failure.

Pravallika KV 18,850 Reputation points Microsoft External Staff Moderator

2026-06-01T16:40:11.76+00:00

@Suma Nalluri , following up to see if you had a chance to check the above response and if it was helpful. Please let me know if you have any questions.
Suma Nalluri 40 Reputation points

2026-06-02T14:27:58.7133333+00:00

Thank you for following up.

I tested the Healthcare Agent Service deployment in the West US 2 region, and the deployment completed successfully using the same subscription and configuration. However, our requirement is to deploy the service in the East US region.

I have verified that Microsoft.HealthBot is registered in the subscription. Since the deployment succeeds in West US 2 but fails in East US, this appears to be specific to the East US region rather than a general subscription or configuration issue.

Could you please advise if there are any known regional restrictions, quota limitations, backend validations, or availability issues affecting Healthcare Agent Service (C1 plan) in East US?
Pravallika KV 18,850 Reputation points Microsoft External Staff Moderator

2026-06-03T01:09:08.06+00:00

AFAIK, there are no publicly documented regional restrictions or special quota limitations that would prevent Healthcare Agent Service (HealthBot) C1 deployments in East US while allowing the same deployment in West US 2.

Since the Microsoft.HealthBot resource provider is registered and the deployment succeeds in West US 2 using the same subscription and configuration, while failing only in East US, the issue appears to be specific to the East US region rather than a subscription, configuration, or provider registration problem:

Regional capacity or availability constraints affecting new HealthBot C1 deployments in East US.

A backend provisioning issue within the HealthBot service specific to the East US region.

A region-specific service validation or platform issue that is not exposed through the generic ARM deployment error.

To confirm the root cause, please share the Correlation ID, deployment timestamp (UTC), and the detailed deployment operation error/Activity Log entry from the failed deployment over private message.

At present, the successful deployment in West US 2 and failure in East US point more toward a regional service-side issue than a subscription, configuration, or provider-registration problem.
Suma Nalluri 40 Reputation points

2026-06-03T15:11:59.0266667+00:00

As requested, please find the deployment details below for investigation:

Correlation ID-<PII removed>

Timestamp-6/3/2026, 11:05:21 AM

Full error message-{

"code": "ResourceDeploymentFailure",

"target": resourceGroups/rg/providers/Microsoft.HealthBot/healthBots/hcas-tcare-callintake-dev-eus",

"message": "The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'."

}

Resource that failed-hcas-tcare-callintake-dev-eus
Pravallika KV 18,850 Reputation points Microsoft External Staff Moderator

2026-06-04T16:24:16.23+00:00

@Suma Nalluri , The issue has been mitigated, could you please try to create the resource now and check if you are still facing the same issue? I have tested the same and its working now.
Suma Nalluri 40 Reputation points

2026-06-04T16:36:55.3566667+00:00

@Pravallika KV I tried it again now I am still facing the same issue
Pravallika KV 18,850 Reputation points Microsoft External Staff Moderator

2026-06-04T16:42:26.81+00:00

Could you please share the error screenshot? and also, which region are you trying to create the resource in?
Suma Nalluri 40 Reputation points

2026-06-04T16:52:48.9833333+00:00

Hi @Pravallika KV I am trying to create the resource in East US region

Operation ID-/subscriptions/****/resourceGroups/rg-care-ai-dev-us/providers/Microsoft.Resources/deployments/Microsoft.HealthBot-20260604123203/operations/F96E9FE2A114EBD4

Status message-{

"status": "Failed",

"error": {

"code": "ResourceDeploymentFailure",

"target": "/subscriptions/***/resourceGroups/rg-care-ai-dev-us/providers/Microsoft.HealthBot/healthBots/hcas-tcare-callintake-dev-eus",

"message": "The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'."

}

}

Resource ID-/subscriptions/****/resourceGroups/rg-care-ai-dev-us/providers/Microsoft.HealthBot/healthBots/hcas-tcare-callintake-dev-eus
Pravallika KV 18,850 Reputation points Microsoft External Staff Moderator

2026-06-04T18:56:50.2366667+00:00

Could you please retry now and confirm? @Suma Nalluri
Suma Nalluri 40 Reputation points

2026-06-04T19:32:43.24+00:00

Hi @Pravallika KV Thank you for your assistance. The issue has been resolved, and the Azure Health Bot deployment is now working successfully in East US region. I appreciate your support and guidance.
Pravallika KV 18,850 Reputation points Microsoft External Staff Moderator

2026-06-04T19:38:25.8733333+00:00

Thanks for the confirmation, glad the issue is resolved @Suma Nalluri . I have posted the answer, please review and do click on and click on Yes for was this answer helpful. And, if you have any further query do let us know.

Answer accepted by question author

Pravallika KV 18,850 Microsoft External Staff Moderator

Hi @Suma Nalluri ,

Thanks for the confirmation, glad the issue is resolved.

We have engaged backend team to investigate the issue. The issue has been mitigated by implementing a Radiance fix and tuning alert configurations to resolve the recurring BotCreateOrUpdate errors.

Hope this helps!

If the resolution was helpful, kindly take a moment to click on User's image and click on Yes for was this answer helpful. And, if you have any further query do let us know.

0 comments

3 additional answers

Your answer

Pravallika KV 18,850 Reputation points Microsoft External Staff Moderator

2026-06-01T16:40:11.76+00:00

@Suma Nalluri , following up to see if you had a chance to check the above response and if it was helpful. Please let me know if you have any questions.
Suma Nalluri 40 Reputation points

2026-06-02T14:27:58.7133333+00:00

Thank you for following up.

I tested the Healthcare Agent Service deployment in the West US 2 region, and the deployment completed successfully using the same subscription and configuration. However, our requirement is to deploy the service in the East US region.

I have verified that Microsoft.HealthBot is registered in the subscription. Since the deployment succeeds in West US 2 but fails in East US, this appears to be specific to the East US region rather than a general subscription or configuration issue.

Could you please advise if there are any known regional restrictions, quota limitations, backend validations, or availability issues affecting Healthcare Agent Service (C1 plan) in East US?
Pravallika KV 18,850 Reputation points Microsoft External Staff Moderator

2026-06-03T01:09:08.06+00:00

AFAIK, there are no publicly documented regional restrictions or special quota limitations that would prevent Healthcare Agent Service (HealthBot) C1 deployments in East US while allowing the same deployment in West US 2.

Since the Microsoft.HealthBot resource provider is registered and the deployment succeeds in West US 2 using the same subscription and configuration, while failing only in East US, the issue appears to be specific to the East US region rather than a subscription, configuration, or provider registration problem:

Regional capacity or availability constraints affecting new HealthBot C1 deployments in East US.

A backend provisioning issue within the HealthBot service specific to the East US region.

A region-specific service validation or platform issue that is not exposed through the generic ARM deployment error.

To confirm the root cause, please share the Correlation ID, deployment timestamp (UTC), and the detailed deployment operation error/Activity Log entry from the failed deployment over private message.

At present, the successful deployment in West US 2 and failure in East US point more toward a regional service-side issue than a subscription, configuration, or provider-registration problem.
Suma Nalluri 40 Reputation points

2026-06-03T15:11:59.0266667+00:00

As requested, please find the deployment details below for investigation:

Correlation ID-<PII removed>

Timestamp-6/3/2026, 11:05:21 AM

Full error message-{

"code": "ResourceDeploymentFailure",

"target": resourceGroups/rg/providers/Microsoft.HealthBot/healthBots/hcas-tcare-callintake-dev-eus",

"message": "The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'."

}

Resource that failed-hcas-tcare-callintake-dev-eus
Pravallika KV 18,850 Reputation points Microsoft External Staff Moderator

2026-06-04T16:24:16.23+00:00

@Suma Nalluri , The issue has been mitigated, could you please try to create the resource now and check if you are still facing the same issue? I have tested the same and its working now.
Suma Nalluri 40 Reputation points

2026-06-04T16:36:55.3566667+00:00

@Pravallika KV I tried it again now I am still facing the same issue
Pravallika KV 18,850 Reputation points Microsoft External Staff Moderator

2026-06-04T16:42:26.81+00:00

Could you please share the error screenshot? and also, which region are you trying to create the resource in?
Suma Nalluri 40 Reputation points

2026-06-04T16:52:48.9833333+00:00

Hi @Pravallika KV I am trying to create the resource in East US region

Operation ID-/subscriptions/****/resourceGroups/rg-care-ai-dev-us/providers/Microsoft.Resources/deployments/Microsoft.HealthBot-20260604123203/operations/F96E9FE2A114EBD4

Status message-{

"status": "Failed",

"error": {

"code": "ResourceDeploymentFailure",

"target": "/subscriptions/***/resourceGroups/rg-care-ai-dev-us/providers/Microsoft.HealthBot/healthBots/hcas-tcare-callintake-dev-eus",

"message": "The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'."

}

}

Resource ID-/subscriptions/****/resourceGroups/rg-care-ai-dev-us/providers/Microsoft.HealthBot/healthBots/hcas-tcare-callintake-dev-eus
Pravallika KV 18,850 Reputation points Microsoft External Staff Moderator

2026-06-04T18:56:50.2366667+00:00

Could you please retry now and confirm? @Suma Nalluri
Suma Nalluri 40 Reputation points

2026-06-04T19:32:43.24+00:00

Hi @Pravallika KV Thank you for your assistance. The issue has been resolved, and the Azure Health Bot deployment is now working successfully in East US region. I appreciate your support and guidance.
Pravallika KV 18,850 Reputation points Microsoft External Staff Moderator

2026-06-04T19:38:25.8733333+00:00

Thanks for the confirmation, glad the issue is resolved @Suma Nalluri . I have posted the answer, please review and do click on and click on Yes for was this answer helpful. And, if you have any further query do let us know.

Answer 1

Enquiries 0

Hi @Abburi, Pravathi (830-Extern-Pravathi) @Keerthana PK

Im having the same issue? UK south

Please advise

thanks

0 comments

Answer 2

Enquiries 0

Hi @Suma Nalluri

I am having the same issue. using UK south.

Please advise?

Thanks

0 comments

Answer 3

Keerthana PK 250 Microsoft Employee

Hi Suma,

Thank you for asking this question on the Microsoft Q&A Platform.

Since you are already ruled out certain possibilities let's check the other possibilities which can go wrong.

Check if the HealthBot service provider is registered in your subscription.

HealthBot (Microsoft.HealthBot) is a specialized provider, not auto-enabled in all subscriptions.

If provider is registered and yet you are facing the issue, try deploying in west us2 region. This confirms if the issue is with region limitation.

Also try downgrading the SKU as part of troubleshooting.

For some partially restricted services like healthbot if you are using Trial/Dev/Test/Sandbox subscription Microsoft needs to explicitly allow your subscription to use that service/SKU.

Let us know if you are able to finetune the issue.

Please Accept the answer if the information helped you. This will help us and others in the community as well!!!

Suma Nalluri 40 Reputation points

2026-06-02T14:23:41.9933333+00:00

Thank you for your response.

I verified that deploying the HealthBot service in the West US 2 region works successfully. However, our requirement is to deploy and use the HealthBot service in the East US region.

Since the deployment succeeds in WUS2 but fails in East US, could you please advise if there are any additional checks, region-specific limitations, quota restrictions, or backend validations that we can perform for East US? If there is any way to enable or troubleshoot HealthBot deployment specifically in East US, I would appreciate your guidance.

Thank you for your help.