Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into retired3

Author: dagiro

articles/active-directory-domain-services/TOC.yml

@@ -49,8 +49,6 @@
       href: ../active-directory/fundamentals/active-directory-whatis.md?context=/azure/active-directory-domain-services/context/azure-ad-ds-context
     - name: Azure Active Directory architecture
       href: ../active-directory/fundamentals/active-directory-architecture.md?context=/azure/active-directory-domain-services/context/azure-ad-ds-context
-    - name: Implement least-privilege administrative models
-      href: /windows-server/identity/ad-ds/plan/security-best-practices/implementing-least-privilege-administrative-models?context=/azure/active-directory-domain-services/context/azure-ad-ds-context
 - name: How to
   items:
     - name: Configure common settings

articles/backup/toc.yml

@@ -1,4 +1,4 @@
-- name: Azure Backup Documentation
+- name: Azure Backup documentation
   href: index.yml
 - name: Overview
   items:

articles/digital-twins/how-to-add-blobs.md

@@ -7,7 +7,7 @@ manager: bertvanhoof
 ms.service: digital-twins
 services: digital-twins
 ms.topic: conceptual
-ms.date: 11/13/2019
+ms.date: 01/10/2020
 ms.custom: seodec18
 ---
 
@@ -31,7 +31,7 @@ In addition to **Content-Type** and **Content-Disposition**, Azure Digital Twins
 
 The four main JSON schemas are:
 
-[![JSON schemas](media/how-to-add-blobs/blob-models-img.png)](media/how-to-add-blobs/blob-models-img.png#lightbox)
+[![JSON schemas](media/how-to-add-blobs/blob-models-swagger-img.png)](media/how-to-add-blobs/blob-models-swagger-img.png#lightbox)
 
 JSON blob metadata conforms to the following model:
 
@@ -191,7 +191,7 @@ curl -X POST "YOUR_MANAGEMENT_API_URL/spaces/blobs" \
 | YOUR_SPACE_ID | The ID of the space to associate the blob with |
 | PATH_TO_FILE | The path to your text file |
 
-[![cURL example](media/how-to-add-blobs/curl-img.png)](media/how-to-add-blobs/curl-img.png#lightbox)
+[![cURL example](media/how-to-add-blobs/http-blob-post-through-curl-img.png)](media/how-to-add-blobs/http-blob-post-through-curl-img.png#lightbox)
 
 A successful POST returns the ID of the new the blob.
 
@@ -203,7 +203,7 @@ The following sections describe the core blob-related API endpoints and their fu
 
 You can attach blobs to devices. The following image shows the Swagger reference documentation for your Management APIs. It specifies device-related API endpoints for blob consumption and any required path parameters to pass into them.
 
-[![Device blobs](media/how-to-add-blobs/blobs-device-api-img.png)](media/how-to-add-blobs/blobs-device-api-img.png#lightbox)
+[![Device blobs](media/how-to-add-blobs/blobs-device-api-swagger-img.png)](media/how-to-add-blobs/blobs-device-api-swagger-img.png#lightbox)
 
 For example, to update or create a blob and attach the blob to a device, make an authenticated HTTP PATCH request to:
 
@@ -221,7 +221,7 @@ Successful requests return a JSON object as [described earlier](#blobs-response-
 
 You can also attach blobs to spaces. The following image lists all space API endpoints responsible for handling blobs. It also lists any path parameters to pass into those endpoints.
 
-[![Space blobs](media/how-to-add-blobs/blobs-space-api-img.png)](media/how-to-add-blobs/blobs-space-api-img.png#lightbox)
+[![Space blobs](media/how-to-add-blobs/blobs-space-api-swagger-img.png)](media/how-to-add-blobs/blobs-space-api-swagger-img.png#lightbox)
 
 For example, to return a blob attached to a space, make an authenticated HTTP GET request to:
 
@@ -241,7 +241,7 @@ A PATCH request to the same endpoint updates metadata descriptions and creates v
 
 You can attach blobs to user models (for example, to associate a profile picture). The following image shows relevant user API endpoints and any required path parameters, like `id`:
 
-[![User blobs](media/how-to-add-blobs/blobs-users-api-img.png)](media/how-to-add-blobs/blobs-users-api-img.png#lightbox)
+[![User blobs](media/how-to-add-blobs/blobs-users-api-swagger-img.png)](media/how-to-add-blobs/blobs-users-api-swagger-img.png#lightbox)
 
 For example, to fetch a blob attached to a user, make an authenticated HTTP GET request with any required form data to:
 
@@ -257,23 +257,41 @@ Successful requests return a JSON object as [described earlier](#blobs-response-
 
 ## Common errors
 
-A common error involves not supplying the correct header information:
+* A common error involves not supplying the correct header information:
 
-```JSON
-{
-    "error": {
-        "code": "400.600.000.000",
-        "message": "Invalid media type in first section."
-    }
-}
-```
+  ```JSON
+  {
+      "error": {
+          "code": "400.600.000.000",
+          "message": "Invalid media type in first section."
+      }
+  }
+  ```
+
+  To resolve this error, verify that the overall request has an appropriate **Content-Type** header:
+
+     * `multipart/mixed`
+     * `multipart/form-data`
+
+  Also, verify that each *multipart chunk* has an appropriate corresponding **Content-Type**.
+
+* A second common error arises when multiple blobs are assigned to the same resource in your [spatial intelligence graph](concepts-objectmodel-spatialgraph.md):
+
+  ```JSON
+  {
+      "error": {
+          "code": "400.600.000.000",
+          "message": "SpaceBlobMetadata already exists."
+      }
+  }
+  ```
 
-To resolve this error, verify that the overall request has an appropriate **Content-Type** header:
+  > [!NOTE]
+  > The **message** attribute will vary based on the resource. 
 
-* `multipart/mixed`
-* `multipart/form-data`
+  Only one blob (of each kind) may be attached to each resource within your spatial graph. 
 
-Also, verify that each multipart chunk has a corresponding **Content-Type** as needed.
+  To resolve this error, update the existing blob by using the appropriate API HTTP PATCH operation. Doing so will replace the existing blob data with the desired data.
 
 ## Next steps
 

articles/digital-twins/how-to-configure-postman.md

@@ -7,7 +7,7 @@ manager: bertvanhoof
 ms.service: digital-twins
 services: digital-twins
 ms.topic: conceptual
-ms.date: 11/13/2019
+ms.date: 01/10/2020
 ---
 
 # How to configure Postman for Azure Digital Twins
@@ -127,6 +127,12 @@ After completing the previous steps, configure Postman to make an authenticated
 
 1. Lastly, select **Send** to submit your multipart HTTP POST request. A status code of `200` or `201` indicates a successful request. The appropriate response message will appear in the client interface.
 
+1. Validate your HTTP POST request data by calling the API endpoint: 
+
+   ```URL
+   YOUR_MANAGEMENT_API_URL/spaces/blobs?includes=description
+   ```
+
 ## Next steps
 
 - To learn about the Digital Twins management APIs, and how to use them, read [How to use Azure Digital Twins management APIs](how-to-navigate-apis.md).

articles/digital-twins/media/how-to-add-blobs/blob-models-img.png renamed to articles/digital-twins/media/how-to-add-blobs/blob-models-swagger-img.png

@@ -83,7 +83,7 @@ The following section describes the configuration of auditing using the Azure po
 5. **New** - You now have multiple options for configuring where audit logs will be written. You can write logs to an Azure storage account, to a Log Analytics workspace for consumption by Azure Monitor logs, or to event hub for consumption using event hub. You can configure any combination of these options, and audit logs will be written to each.
 
   > [!NOTE]
-   >Customer wishing to configure an immutable log store for their server- or database-level audit events should follow the [instructions provided by Azure Storage] (https://docs.microsoft.com/azure/storage/blobs/storage-blob-immutable-storage)
+   >Customer wishing to configure an immutable log store for their server- or database-level audit events should follow the [instructions provided by Azure Storage](https://docs.microsoft.com/azure/storage/blobs/storage-blob-immutability-policies-manage#enabling-allow-protected-append-blobs-writes)
   
   > [!WARNING]
    > Enabling auditing to Log Analytics will incur cost based on ingestion rates. Please be aware of the associated cost with using this [option](https://azure.microsoft.com/pricing/details/monitor/), or consider storing the audit logs in an Azure storage account.