Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into rolyon-rbac-horizontal-rbac-terms

Author: rolyon

articles/event-hubs/event-hubs-diagnostic-logs.md

@@ -26,8 +26,8 @@ You can view two types of logs for Azure Event Hubs:
 * **[Activity logs](../azure-monitor/platform/platform-logs-overview.md)**: These logs have information about operations done on a job. The logs are always enabled. You can see activity log entries by selecting **Activity log** in the left pane for your event hub namespace in the Azure portal. For example: "Create or Update Namespace", "Create or Update Event Hub".
 
     ![Activity log for an Event Hubs namespace](./media/event-hubs-diagnostic-logs/activity-log.png)
-* **[Diagnostic logs](../azure-monitor/platform/platform-logs-overview.md)**: You can configure diagnostic logs for a richer view of everything that happens with a job. Diagnostic logs cover activities from the time the job is created until the job is deleted, including updates and activities that occur while the job is running.
-
+* **[Diagnostic logs](../azure-monitor/platform/platform-logs-overview.md)**: Diagnostic logs provide richer information about operations and actions that are conducted against your namespace by using the API, or through management clients on the language SDK. 
+    
     The following section shows you how to enable diagnostic logs for an Event Hubs namespace.
 
 ## Enable diagnostic logs
@@ -51,45 +51,47 @@ Diagnostic logs are disabled by default. To enable diagnostic logs, follow these
 
 Event Hubs captures diagnostic logs for the following categories:
 
-- **Archive Logs**: logs related to Event Hubs archives, specifically, logs related to archive errors.
-- **Operational Logs**: information about what is happening during Event Hubs operations, specifically, the operation type, including event hub creation, resources used, and the status of the operation.
-- **Auto scale logs**: information about autoscaling operations done on an Event Hubs namespace. 
-- **Kafka coordinator logs** - information about Kafka coordinator operations related to Event Hubs. 
-- **Kafka user logs**: information about Kafka user operations related to Event Hubs. 
-- **Event Hubs virtual network (VNet) connection event**: information about Event Hubs virtual network connection events. 
-- **Customer-managed key user logs**: information about operations related to customer-managed key. 
+| Category | Description | 
+| -------- | ----------- | 
+| Archive Logs | Captures information about [Event Hubs Capture](event-hubs-capture-overview.md) operations, specifically, logs related to capture errors. |
+| Operational Logs | Capture all management operations that are performed on the Azure Event Hubs namespace. Data operations are not captured, because of the high volume of data operations that are conducted on Azure Event Hubs. |
+| Auto scale logs | Captures auto-inflate operations done on an Event Hubs namespace. |
+| Kafka coordinator logs | Captures Kafka coordinator operations related to Event Hubs. |
+| Kafka user error logs | Captures information about Kafka APIs called on Event Hubs. |
+| Event Hubs virtual network (VNet) connection event | Captures information about IP addresses and virtual networks sending traffic to Event Hubs. |
+| Customer-managed key user logs | Captures operations related to customer-managed key. |
 
 
-    All logs are stored in JavaScript Object Notation (JSON) format. Each entry has string fields that use the format described in the following sections.
+All logs are stored in JavaScript Object Notation (JSON) format. Each entry has string fields that use the format described in the following sections.
 
 ## Archive logs schema
 
 Archive log JSON strings include elements listed in the following table:
 
 Name | Description
 ------- | -------
-TaskName | Description of the task that failed.
-ActivityId | Internal ID, used for tracking.
-trackingId | Internal ID, used for tracking.
-resourceId | Azure Resource Manager resource ID.
-eventHub | Event hub full name (includes namespace name).
-partitionId | Event Hub partition being written to.
-archiveStep | ArchiveFlushWriter
-startTime | Failure start time.
-failures | Number of times failure occurred.
-durationInSeconds | Duration of failure.
-message | Error message.
+TaskName | Description of the task that failed
+ActivityId | Internal ID, used for tracking
+trackingId | Internal ID, used for tracking
+resourceId | Azure Resource Manager resource ID
+eventHub | Event hub full name (includes namespace name)
+partitionId | Event Hub partition being written to
+archiveStep | possible values: ArchiveFlushWriter, DestinationInit
+startTime | Failure start time
+failures | Number of times the failure occurred
+durationInSeconds | Duration of failure
+message | Error message
 category | ArchiveLogs
 
 The following code is an example of an archive log JSON string:
 
 ```json
 {
    "TaskName": "EventHubArchiveUserError",
-   "ActivityId": "21b89a0b-8095-471a-9db8-d151d74ecf26",
-   "trackingId": "21b89a0b-8095-471a-9db8-d151d74ecf26_B7",
-   "resourceId": "/SUBSCRIPTIONS/854D368F-1828-428F-8F3C-F2AFFA9B2F7D/RESOURCEGROUPS/DEFAULT-EVENTHUB-CENTRALUS/PROVIDERS/MICROSOFT.EVENTHUB/NAMESPACES/FBETTATI-OPERA-EVENTHUB",
-   "eventHub": "fbettati-opera-eventhub:eventhub:eh123~32766",
+   "ActivityId": "000000000-0000-0000-0000-0000000000000",
+   "trackingId": "0000000-0000-0000-0000-00000000000000000",
+   "resourceId": "/SUBSCRIPTIONS/000000000-0000-0000-0000-0000000000000/RESOURCEGROUPS/<Resource Group Name>/PROVIDERS/MICROSOFT.EVENTHUB/NAMESPACES/<Event Hubs Namespace Name>",
+   "eventHub": "<Event Hub full name>",
    "partitionId": "1",
    "archiveStep": "ArchiveFlushWriter",
    "startTime": "9/22/2016 5:11:21 AM",
@@ -106,27 +108,27 @@ Operational log JSON strings include elements listed in the following table:
 
 Name | Description
 ------- | -------
-ActivityId | Internal ID, used to track purpose.
-EventName | Operation name.	 
-resourceId | Azure Resource Manager resource ID.
-SubscriptionId | Subscription ID.
-EventTimeString | Operation time.
-EventProperties | Operation properties.
-Status | Operation status.
-Caller | Caller of operation (Azure portal or management client).
-category | OperationalLogs
+ActivityId | Internal ID, used for tracking purposes |
+EventName | Operation name |
+resourceId | Azure Resource Manager resource ID |
+SubscriptionId | Subscription ID |
+EventTimeString | Operation time |
+EventProperties | Operation properties |
+Status | Operation status |
+Caller | Caller of operation (Azure portal or management client) |
+Category | OperationalLogs |
 
 The following code is an example of an operational log JSON string:
 
 ```json
 Example:
 {
-   "ActivityId": "6aa994ac-b56e-4292-8448-0767a5657cc7",
+   "ActivityId": "00000000-0000-0000-0000-00000000000000",
    "EventName": "Create EventHub",
-   "resourceId": "/SUBSCRIPTIONS/1A2109E3-9DA0-455B-B937-E35E36C1163C/RESOURCEGROUPS/DEFAULT-SERVICEBUS-CENTRALUS/PROVIDERS/MICROSOFT.EVENTHUB/NAMESPACES/SHOEBOXEHNS-CY4001",
-   "SubscriptionId": "1a2109e3-9da0-455b-b937-e35e36c1163c",
+   "resourceId": "/SUBSCRIPTIONS/00000000-0000-0000-0000-0000000000000/RESOURCEGROUPS/<Resource Group Name>/PROVIDERS/MICROSOFT.EVENTHUB/NAMESPACES/<Event Hubs namespace name>",
+   "SubscriptionId": "000000000-0000-0000-0000-000000000000",
    "EventTimeString": "9/28/2016 8:40:06 PM +00:00",
-   "EventProperties": "{\"SubscriptionId\":\"1a2109e3-9da0-455b-b937-e35e36c1163c\",\"Namespace\":\"shoeboxehns-cy4001\",\"Via\":\"https://shoeboxehns-cy4001.servicebus.windows.net/f8096791adb448579ee83d30e006a13e/?api-version=2016-07\",\"TrackingId\":\"5ee74c9e-72b5-4e98-97c4-08a62e56e221_G1\"}",
+   "EventProperties": "{\"SubscriptionId\":\"0000000000-0000-0000-0000-000000000000\",\"Namespace\":\"<Namespace Name>\",\"Via\":\"https://<Namespace Name>.servicebus.windows.net/f8096791adb448579ee83d30e006a13e/?api-version=2016-07\",\"TrackingId\":\"5ee74c9e-72b5-4e98-97c4-08a62e56e221_G1\"}",
    "Status": "Succeeded",
    "Caller": "ServiceBus Client",
    "category": "OperationalLogs"

articles/event-hubs/move-across-regions.md

@@ -24,7 +24,7 @@ There are various scenarios in which you'd want to move your existing Event Hubs
 - Ensure that the services and features that your account uses are supported in the target region.
 - For preview features, ensure that your subscription is whitelisted for the target region.
 - If you have **capture feature** enabled for event hubs in the namespace, move [Azure Storage or Azure Data Lake Store Gen 2](../storage/common/storage-account-move.md) or [Azure Data Lake Store Gen 1](../data-lake-store/data-lake-store-migration-cross-region.md) accounts before moving the Event Hubs namespace. You can also move the resource group that contains both Storage and Event Hubs namespaces to the other region by following steps similar to the ones described in this article. 
-- If the Event Hubs namespace is in an **Event Hubs cluster**, [create a dedicated cluster](event-hubs-dedicated-cluster-create-portal.md) in the **target region** before you go through steps in this article. 
+- If the Event Hubs namespace is in an **Event Hubs cluster**, [create a dedicated cluster](event-hubs-dedicated-cluster-create-portal.md) in the **target region** before you go through steps in this article. You can also use the [quickstart template on GitHub](https://github.com/Azure/azure-quickstart-templates/tree/master/201-eventhubs-create-cluster-namespace-eventhub/) to create an Event Hubs cluster. In the template, remove the namespace portion of the JSON to create only the cluster. 
 
 ## Prepare
 To get started, export a Resource Manager template. This template contains settings that describe your Event Hubs namespace.

articles/media-services/azure-media-player/azure-media-player-known-issues.md

@@ -41,9 +41,10 @@ The current release has the following known issues:
 
 - In the DVR window of Live content, when content finishes the timeline will continue to grow until seeking to the area or reaching the end of the presentation.
 - Live presentations in Firefox with MSE enabled has some issues
-- Assets that are audio or video only won't play back via the AzureHtml5JS tech.
-  - If you'd like to play back assets without audio or video, you can do so by inserting blank audio or video using the [Azure Media Services Explorer tool](https://aka.ms/amse)
-    - Instructions on how to insert silent audio can be found [here](https://azure.microsoft.com/documentation/articles/media-services-advanced-encoding-with-mes/#silent_audio)
+
+- Assets that are audio only will not play back via the AzureHtml5JS tech.
+  - If you’d like to play back assets without audio, you can do so by inserting blank audio using the [Azure Media Services Explorer tool](https://aka.ms/amse)
+  - Instructions on how to insert silent audio can be found [here](https://azure.microsoft.com/documentation/articles/media-services-advanced-encoding-with-mes/#silent_audio)
 
 ## Flash ##
 
@@ -86,7 +87,7 @@ The current release has the following known issues:
 ## Apple ##
 
 - Safari on Mac often enables Power Saver mode by default with the setting "Stop plug-ins to save power", which blocks plugins like Flash and Silverlight when they believe it is not in favor to the user. This block does not block the plugin's existent, only capabilities. Given the default techOrder, this may cause issues when attempting to play back
-  - Mitigation 1: If the video player is 'front and center' (within a 3000 x 3000 pixel boundary starting at the top left corner of the document), it should still play.
+  - Mitigation 1: If the video player is 'front and center' (within a 3000 x 3000 pixel boundary starting at the top-left corner of the document), it should still play.
   - Mitigation 2: Change the techOrder for Safari to be ["azureHtml5JS", "html5"]. This mitigation has implication of not getting all the features that are available in the FlashSS tech.
 - PlayReady content via Silverlight may have issues playing back in Safari.
 - AES and restricted token content does not play back using iOS and older Android devices.