Merge pull request #107065 from Juliako/portal

Portal

Author: GitHubber17

articles/media-services/latest/TOC.yml

@@ -206,11 +206,15 @@
   items:
   - name: Get started
     items:
+    - name: Create an account - portal
+      href: create-account-portal.md
     - name: Create an account - CLI
       href: create-account-cli-how-to.md  
       displayName: storage
     - name: Reset the account credentials - CLI
-      href: cli-reset-account-credentials.md      
+      href: cli-reset-account-credentials.md   
+    - name: Access APIs - portal
+      href: access-api-portal.md   
     - name: Access APIs - CLI
       href: access-api-cli-how-to.md
     - name: Scale Media Reserved Units - CLI

articles/media-services/latest/access-api-portal.md

@@ -0,0 +1,64 @@
+---
+title: Get started with Azure AD authentication by using the Azure portal
+description: Learn how to use the Azure portal to access Azure Active Directory (Azure AD) authentication to consume the Azure Media Services API. 
+services: media-services
+documentationcenter: ''
+author: Juliako
+manager: femila
+editor: ''
+
+ms.service: media-services
+ms.workload: media
+ms.tgt_pltfrm: na
+ms.devlang: na
+ms.topic: how-to
+ms.date: 03/09/2020
+ms.author: juliako
+---
+# Use the Azure portal to get credentials to access Media Services API  
+
+When you use Azure AD authentication to access the Azure Media Services API, you have two authentication options:
+
+- **Service principal authentication**. Authenticate a service. Applications that commonly use this authentication method are apps that run daemon services, middle-tier services, or scheduled jobs: web apps, function apps, logic apps, APIs, or a microservice.
+- **User authentication**. Authenticate a person who is using the app to interact with Media Services resources. The interactive application should first prompt the user for credentials. An example is a management console app used by authorized users to monitor encoding jobs or live streaming. 
+
+This article shows you how to use the Azure portal to get credentials to access Media Services API.
+
+## Prerequisites
+
+- An Azure account. If you don't have an account, start with an [Azure free trial](https://azure.microsoft.com/pricing/free-trial/). 
+- A Media Services account. For more information, see [Create an Azure Media Services account by using the Azure portal](create-account-portal.md).
+
+## API access 
+
+The **API access** page lets you select the authentication method you want to use to connect to the API. The page also provides the values you need to connect to the API.
+
+1. In the [Azure portal](https://portal.azure.com/), select your Media Services account.
+2. Select how to connect to the Media Services API.
+3. Under **Connect to Media Services API**, select the Media Services API version you want to connect to (V3 is the latest version of the service).
+
+## Service principal authentication  (recommended)
+
+Authenticates a service using an Azure Active Directory (Azure AD) app and secret. This is recommended for any middle-tier services calling to the Media Services API. Examples are Web Apps, Functions, Logic Apps, APIs, and microservices. This is the recommended authentication method.
+
+### Manage your Azure AD app and secret
+
+The **Manage your AAD app and secret** section lets you select or create a new Azure AD app and generate a secret. For security purposes, the secret cannot be shown after the blade is closed. The application uses the application ID and secret for authentication to obtain a valid token for media services.
+
+Make sure that you have sufficient permissions to register an application with your Azure AD tenant and to assign the application to a role in your Azure subscription. For more information, see [Required permissions](https://docs.microsoft.com/azure/active-directory/develop/howto-create-service-principal-portal#required-permissions).
+
+### Connect to Media Services API
+
+The **Connect to Media Services API** provides you with values that you use to connect your service principal application. You can get text values or copy the JSON or XML blocks.
+
+## User authentication
+
+This option could be used to authenticate an employee or member of an Azure Active Directory who is using an app to interact with Media Services resources. The interactive application should first prompt the user for the user's credentials. This authentication method should only be used for Management applications.
+
+### Connect to Media Services API
+
+Copy your credentials to connect your user application from the **Connect to Media Services API** section. You can get text values or copy the JSON or XML blocks.
+
+## Next steps
+
+[Tutorial: Upload, encode, and stream videos with Media Services v3](stream-files-tutorial-with-api.md).

articles/media-services/latest/create-account-portal.md

@@ -0,0 +1,59 @@
+---
+title: Create an Azure Media Services account with the Azure portal 
+description: This tutorial walks you through the steps of creating an Azure Media Services account with the Azure portal.
+services: media-services
+documentationcenter: ''
+author: Juliako
+manager: femila
+editor: ''
+
+ms.service: media-services
+ms.workload: media
+ms.tgt_pltfrm: na
+ms.devlang: na
+ms.topic: how-to
+ms.date: 03/09/2020
+ms.author: juliako
+
+---
+# Use the Azure portal to create a Media Services account
+
+The Azure portal provides a way to quickly create an Azure Media Services account. You can use your account to access Media Services that enable you to store, encrypt, encode, manage, and stream media content in Azure.
+
+This article shows how to create a Media Services account using the Azure portal.
+
+## Prerequisites
+
+To complete this tutorial, you need an Azure account. For details, see [Azure Free Trial](https://azure.microsoft.com/pricing/free-trial/). 
+
+## Create a Media Services account
+
+1. Sign in at the [Azure portal](https://portal.azure.com/).
+1. Click **+Create a resource** > **Media** > **Media Services**.
+1. In **CREATE MEDIA SERVICES ACCOUNT** enter required values.
+    
+    | Name | Description |
+    | ---|---|
+    |**Account Name**|Enter the name of the new Media Services account. A Media Services account name is all lowercase letters or numbers with no spaces, and is 3 to 24 characters in length.|
+    |**Subscription**|If you have more than one subscription, select one from the list of Azure subscriptions that you have access to.|
+    |**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](../../azure-resource-manager/management/overview.md#resource-groups).|
+    |**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. |
+    |**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 new 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.<br/><br/>You must have one **Primary** storage account and you can have any number of **Secondary** storage accounts associated with your Media Services account. You can use the Azure portal to add secondary storage accounts. For more information, see [Azure Storage accounts with Azure Media Services accounts](storage-account-concept.md).<br/><br/>The Media Services account and all associated storage accounts must be in the same Azure subscription. It is strongly recommended to use storage accounts in the same location as the Media Services account to avoid additional latency and data egress costs.|
+    
+1. Select **Pin to dashboard** to see the progress of the account deployment.
+1. 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 Media Services 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](dynamic-packaging-overview.md) and [dynamic encryption](content-protection-overview.md), the streaming endpoint from which you want to stream content has to be in the **Running** state. 
+
+> [!NOTE]
+> You can use the [Azure portal](https://portal.azure.com/) to manage v3 [Live Events](live-events-outputs-concept.md), view v3 [Assets](assets-concept.md), get info about accessing APIs. For all other management tasks (for example, Transforms and Jobs), use the [REST API](https://aka.ms/ams-v3-rest-ref), [CLI](https://aka.ms/ams-v3-cli-ref), or one of the supported [SDKs](media-services-apis-overview.md#sdks).
+
+## Next steps
+
+If you plan to access Media Services API programmatically, see [Access the Azure Media Services API with Azure AD authentication](access-api-portal.md).
+
+## Provide feedback
+[!INCLUDE [media-services-user-voice-include](../../../includes/media-services-user-voice-include.md)]
+