Create a Media Services account using the Azure portal
Update your Azure Media Services REST API and SDKs to v3 by 29 February 2024. Version 3 of Azure Media Services REST API and client SDKs for .NET and Java offers more capabilities than version 2. We’re retiring version 2 of the Azure Media Services REST API and client SDKs for .NET and Java.
Action Required: To minimize disruption to your workloads, review the migration guide to transition your code from the version 2 API and SDKs to version 3 API and SDK before February 29th, 2024. After February 29th, 2024, Azure Media Services will no longer accept traffic on the version 2 REST API, the ARM account management API version 2015-10-01, or from the version 2 .NET client SDKs. This includes any 3rd party open-source client SDKS that may call the version 2 API. Learn about the latest version, starting with the Media Services v3 Overview.
The Azure portal provides a way to quickly create an Azure Media Services (AMS) account. You can use your account to access Media Services that enable you to store, encrypt, encode, manage, and stream media content in Azure. At the time you create a Media Services account, you also create an associated storage account (or use an existing one). If you delete a Media Services account, the blobs in your related storage account are not deleted. UD The Media Services account and all associated storage accounts must be in the same Azure subscription. You are strongly encouraged to use storage accounts in the same location as the Media Services account to avoid additional latency and data egress costs.
This article shows how to create a Media Services account using the Azure portal.
For information about availability of Azure Media Services features in different regions, see AMS features across regions.
To complete this tutorial, you need an Azure account. For details, see Azure Free Trial.
Create an AMS account
The steps in this section show how to create an AMS account.
Sign in at the Azure portal.
Click +Create a resource > Media > Media Services.
In CREATE MEDIA SERVICES ACCOUNT enter required values.
In Account Name, enter the name of the new AMS account. A Media Services account name is all lowercase letters or numbers with no spaces, and is 3 to 24 characters in length.
In Subscription, select among the different Azure subscriptions that you have access to.
In Resource Group, select the new or existing resource. A resource group is a collection of resources that share lifecycle, permissions, and policies. Learn more here.
In Location, select the geographic region that will be used to store the media and metadata records for your Media Services account. This region will be used to process and stream your media. Only the available Media Services regions appear in the drop-down list box.
In Storage Account, select a storage account to provide blob storage of the media content from your Media Services account. You can select an existing storage account in the same geographic region as your Media Services account, or you can create a storage account. A new storage account is created in the same region. The rules for storage account names are the same as for Media Services accounts.
Learn more about storage here.
Select Pin to dashboard to see the progress of the account deployment.
Click Create at the bottom of the form.
Once the account is successfully created, overview page loads. In the streaming endpoint table the account will have a default streaming endpoint in the Stopped state.
When your AMS account is created a default streaming endpoint is added to your account in the Stopped state. To start streaming your content and take advantage of dynamic packaging and dynamic encryption, the streaming endpoint from which you want to stream content has to be in the Running state.
To manage your AMS account
To manage your AMS account (for example, connect to the AMS API programmatically, upload videos, encode assets, configure content protection, monitor job progress) select Settings on the left side of the portal. From the Settings, navigate to one of the available blades (for example: API access, Assets, Jobs, Content protection).