Microsoft Azure HealthcareApisClient

What authentication does this API use?

The control-plane API uses Azure AD OAuth2 against management.azure.com, declared as the azure_auth security scheme. The data plane (FHIR access on each provisioned service) uses a separate Azure AD authority configured per service. Through Jentic, your service principal credentials sit encrypted in the vault and are exchanged for a scoped bearer token at execution.

Does this API let me read or write FHIR resources?

No. This is the management/control-plane API for Healthcare APIs services. It provisions and configures service instances. To read or write FHIR resources (Patient, Observation, Encounter, etc.) you call the FHIR endpoint of a provisioned service, which speaks the FHIR REST standard, not this ARM API.

What are the rate limits?

Standard ARM throttles apply at the subscription level - about 12,000 reads and 1,200 writes per hour per subscription. Provisioning is long-running, so PUT calls return 202 and callers should poll the operationresults endpoint rather than retry.

How do I provision a FHIR service through Jentic?

Run jentic.search('create azure healthcare apis service'), load the Services_CreateOrUpdate schema, and execute it with the subscription, resource group, service name, location, kind (such as 'fhir-R4'), and the Azure AD auth configuration. Once the operationresults endpoint reports Succeeded, the FHIR endpoint hostname is available on the resource.

Can I limit what my agent is allowed to do with the Azure Healthcare APIs Management API?

Yes. Because you run Jentic One yourself, your own rules decide which of this API's operations the agent may call, so you can allow the read and check-name-availability operations while withholding create, patch, and delete on a Healthcare APIs service. Since the service name travels in the URL path under /services/{resourceName}, a rule can pin the agent to reading and checking specific named services rather than acting across the whole subscription. Deleting a Healthcare APIs service stays off the table unless you explicitly grant it, and the Azure service principal credentials never enter the agent's prompt or context.