Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into rolyon-rbac-mg-custom-roles

Author: rolyon

articles/automation/automation-first-runbook-graphical.md

@@ -123,9 +123,10 @@ Now that you have a variable to hold the subscription ID, you can configure the
 1. Navigate to your runbook and select **Edit** on the **MyFirstRunbook-Graphical** page.
 1. You don't need the `Write Hello World to output` entry any more. Just click the ellipsis and select **Delete**.
 1. In the Library control, expand **ASSETS**, then **Connections**. Add `AzureRunAsConnection` to the canvas by selecting **Add to canvas**.
+1. Rename `AzureRunAsConnection` to `Get Run As Connection`.
 1. In the Library control, type `Connect-AzAccount` in the search field.
 1. Add `Connect-AzAccount` to the canvas.
-1. Hover over **Get Run As Connection** until a circle appears on the bottom of the shape. Click the circle and drag the arrow to `Connect-AzAccount` to form a link. The runbook starts with `Get Run As Connection` and then runs `Connect-AzAccount`.<br> ![Create link between activities](media/automation-first-runbook-graphical/runbook-link-auth-activities.png)
+1. Hover over `Get Run As Connection` until a circle appears on the bottom of the shape. Click the circle and drag the arrow to `Connect-AzAccount` to form a link. The runbook starts with `Get Run As Connection` and then runs `Connect-AzAccount`.<br> ![Create link between activities](media/automation-first-runbook-graphical/runbook-link-auth-activities.png)
 1. On the canvas, select `Connect-AzAccount`. In the Configuration control pane, type **Login to Azure** in the **Label** field.
 1. Click **Parameters**, and the Activity Parameter Configuration page appears.
 1. The `Connect-AzAccount` cmdlet has multiple parameter sets, and you need to select one before providing parameter values. Click **Parameter Set** and then select **ServicePrincipalCertificateWithSubscriptionId**.

articles/automation/automation-windows-hrw-install.md

@@ -21,7 +21,7 @@ After you successfully deploy a runbook worker, review [Run runbooks on a Hybrid
 
 To install and configure a Windows Hybrid Runbook Worker, you can use one of the following methods.
 
-* For Azure VMs, install the Log Analytics agent for Windows using the [virtual machine extension for Windows](../virtual-machines/extensions/oms-windows.md). The extension installs the Log Analytics agent on Azure virtual machines, and enrolls virtual machines into an existing Log Analytics workspace using an Azure Resource Manager template or PowerShell. Once the agent is installed, the VM can be added to a Hybrid Runbook Worker group in your Automation account following step 4 in the [Manual deployment](#manual-deployment) section.
+* For Azure VMs, install the Log Analytics agent for Windows using the [virtual machine extension for Windows](../virtual-machines/extensions/oms-windows.md). The extension installs the Log Analytics agent on Azure virtual machines, and enrolls virtual machines into an existing Log Analytics workspace using an Azure Resource Manager template or PowerShell. Once the agent is installed, the VM can be added to a Hybrid Runbook Worker group in your Automation account. Refer to steps 3 and 4 in the [Manual deployment](#manual-deployment) section.
 
 * Use an Automation runbook to completely automate the process of configuring a Windows computer. This is the recommended method for machines in your datacenter or another cloud environment.
 

articles/automation/media/automation-first-runbook-graphical/runbook-auth-config.png

@@ -113,7 +113,7 @@
   - name: Packaging and delivery
     items:
     - name: Dynamic packaging
-      displayName: origin, packager, HLS, DASH, CMAF, Smooth, manifest, deliver, format, URL, streaming  
+      displayName: origin, packager, HLS, DASH, CMAF, Smooth, manifest, deliver, format, URL, streaming, audio, video 
       href: dynamic-packaging-overview.md
     - name: Dynamic manifests
       href: filters-dynamic-manifest-overview.md 

articles/automation/media/automation-first-runbook-graphical/runbook-link-auth-activities.png

@@ -13,7 +13,7 @@ ms.workload: media
 ms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: overview
-ms.date: 03/09/2020 
+ms.date: 03/17/2020 
 ms.author: juliako
 #Customer intent: As a developer or content provider, I want to encode and stream on-demand or live content so my customers can view the content on a wide variety of clients (these clients understand different formats).
 ---
@@ -68,6 +68,9 @@ Your streaming client can specify the following Smooth Streaming formats:
 |Smooth Streaming| `https://amsv3account-usw22.streaming.media.azure.net/21b17732-0112-4d76-b526-763dcd843449/ignite.ism/manifest`||
 |Smooth Streaming 2.0 (legacy manifest)|By default, Smooth Streaming manifest format contains the repeat tag (r-tag). However, some players do not support the `r-tag`. Clients with these players can use a format that disables the r-tag:<br/><br/>`https://amsv3account-usw22.streaming.media.azure.net/21b17732-0112-4d76-b526-763dcd843449/ignite.ism/manifest(format=fmp4-v20)`|
 
+> [!NOTE]
+> Smooth Streaming requires that both audio and video should be present in your stream.
+
 ## On-demand streaming workflow
 
 The following steps show a common Media Services streaming workflow where Dynamic Packaging is used along with the Standard Encoder in Azure Media Services.

articles/automation/media/automation-first-runbook-graphical/runbook-startazurermvm-complete.png

@@ -18,7 +18,7 @@ ms.author: juliako
 
 # Streaming Endpoints (Origin) in Azure Media Services
 
-In Microsoft Azure Media Services, a [Streaming Endpoint](https://docs.microsoft.com/rest/api/media/streamingendpoints) represents a dynamic (just-in-time) packaging and origin service that can deliver your live and on-demand content directly to a client player app using one of the common streaming media protocols (HLS or DASH). In addition, the **Streaming Endpoint** provides dynamic (just-in-time) encryption to industry-leading DRMs.
+In Microsoft Azure Media Services, a [Streaming Endpoint](https://docs.microsoft.com/rest/api/media/streamingendpoints) represents a dynamic (just-in-time) packaging and origin service that can deliver your live and on-demand content directly to a client player app using one of the common streaming media protocols (HLS or DASH). In addition, the **Streaming Endpoint** provides dynamic (just-in-time) encryption to industry-leading DRMs. 
 
 When you create a Media Services account, a **default** Streaming Endpoint is created for you in a stopped state. You can't delete the **default** Streaming Endpoint. More Streaming Endpoints can be created under the account (see [Quotas and limitations](limits-quotas-constraints.md)).
 
@@ -27,6 +27,8 @@ When you create a Media Services account, a **default** Streaming Endpoint is cr
 >
 > You're only billed when your Streaming Endpoint is in the running state.
 
+Make sure to also review the [Dynamic packaging](dynamic-packaging-overview.md) topic. 
+
 ## Naming convention
 
 The host name format of the streaming URL is: `{servicename}-{accountname}-{regionname}.streaming.media.azure.net`, where 
@@ -155,10 +157,14 @@ See the following articles:
 - [CDN overview](../../cdn/cdn-overview.md)
 - [Scaling streaming with CDN](scale-streaming-cdn.md)
 
-## Ask questions, give feedback, get updates
+## Ask questions and  get updates
 
 Check out the [Azure Media Services community](media-services-community.md) article to see different ways you can ask questions, give feedback, and get updates about Media Services.
 
+## See also
+
+[Dynamic packaging](dynamic-packaging-overview.md)
+
 ## Next steps
 
 [Manage streaming endpoints](manage-streaming-endpoints-howto.md)