Microsoft Azure MediaServicesManagementClient

What authentication does the Media Services Management API use?

The API uses Azure Active Directory OAuth 2.0 via the azure_auth scheme on https://management.azure.com/. Through Jentic, your Azure AD application credentials are stored encrypted in your Jentic One instance and exchanged for a short-lived bearer token at execution time.

Can I provision a Media Services account with this API?

Yes. Call PUT /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Media/mediaservices/{mediaServiceName} with location and a storageAccounts list referencing the backing Azure Storage account. The new account is ready to receive data-plane calls once provisioning succeeds.

What are the rate limits for the Media Services Management API?

The control-plane endpoints inherit standard Azure Resource Manager throttle quotas, surfaced through x-ms-ratelimit-remaining-* response headers. Bulk creation or rotation operations should respect those headers and back off when remaining quota approaches zero.

How do I rotate Media Services keys through Jentic?

Search Jentic for 'rotate azure media services keys', load MediaService_RegenerateKey, supply the keyType (primary or secondary) in the body, and execute. The response returns the new key, which the agent can then push to downstream consumers.

Does this API also encode or stream video?

No. This is the management plane for the account itself. Data-plane operations such as creating assets, jobs, encoding presets, and streaming endpoints are handled via the Media Services data plane, which is separate from this resource provider API.

What happens if I forget to sync storage keys after rotation?

Streaming and encoding workloads will start to fail with authorisation errors against the backing storage account. Calling POST /.../syncStorageKeys forces Media Services to re-fetch the latest storage keys, immediately restoring access without recreating the account.

Can I limit what my agent is allowed to do with the Media Services Management API?

Yes. Because Jentic One is self-hosted, your own rules decide which operations and credentials the agent may use, and the subscription, resource group, and media service name sit in the URL path so you can pin the agent to a single Media Services account. You choose the exact operations it may call, so you can allow it to read the account and sync storage keys while excluding destructive ones like deleting the account or regenerating its keys. The Azure AD credential stays encrypted in your instance and is exchanged for a short-lived token at execution time, so the agent never sees the raw secret.