Clarify blob requirements

Author: baanders

articles/digital-twins/concepts-apis-sdks.md

@@ -142,8 +142,9 @@ Once the file has been created, upload it to a block blob in Azure Blob Storage
 
 Now you can proceed with calling the [Jobs API](/rest/api/digital-twins/dataplane/import-jobs). For detailed instructions on importing a full graph in one API call, see  [Upload models, twins, and relationships in bulk with the Jobs API](how-to-manage-graph.md#upload-models-twins-and-relationships-in-bulk-with-the-jobs-api). You can also use the Jobs API to import each resource type independently. For more information on using the Jobs API with individual resource types, see Jobs API instructions for [models](how-to-manage-model.md#upload-large-model-sets-with-the-jobs-api), [twins](how-to-manage-twin.md#create-twins-in-bulk-with-the-jobs-api), and [relationships](how-to-manage-graph.md#create-relationships-in-bulk-with-the-jobs-api).
 
-In the body of the API call, you'll provide the blob storage URL of the NDJSON input file, as well as another blob storage URL for where you'd like the output log to be stored.
-As the import job executes, a structured output log is generated by the service and stored as a new append blob in your blob container, according to the output blob URL and name you provided. Here's an example output log for a successful job importing models, twins, and relationships:
+In the body of the API call, you'll provide the blob storage URL of the NDJSON input file. You'll also provide a new blob storage URL to indicate where you'd like the output log to be stored once the service creates it. 
+
+As the import job executes, a structured output log is generated by the service and stored as a new append blob in your blob container, at the URL location you specified for the output blob in the request. Here's an example output log for a successful job importing models, twins, and relationships:
 
 ```json
 {"timestamp":"2022-12-30T19:50:34.5540455Z","jobId":"test1","jobType":"Import","logType":"Info","details":{"status":"Started"}}

articles/digital-twins/how-to-manage-graph.md

@@ -89,7 +89,7 @@ You can view an example import file and a sample project for creating these file
 
 [!INCLUDE [digital-twins-bulk-blob.md](../../includes/digital-twins-bulk-blob.md)]
 
-Then, the file can be used in an [Jobs API](/rest/api/digital-twins/dataplane/import-jobs) call.
+Then, the file can be used in an [Jobs API](/rest/api/digital-twins/dataplane/import-jobs) call. You'll provide the blob storage URL of the input file, as well as a new blob storage URL to indicate where you'd like the output log to be stored when it's created by the service.
 
 ## List relationships
 
@@ -188,7 +188,7 @@ You can view an example import file and a sample project for creating these file
 
 [!INCLUDE [digital-twins-bulk-blob.md](../../includes/digital-twins-bulk-blob.md)]
 
-Then, the file can be used in an [Jobs API](/rest/api/digital-twins/dataplane/import-jobs) call.
+Then, the file can be used in an [Jobs API](/rest/api/digital-twins/dataplane/import-jobs) call. You'll provide the blob storage URL of the input file, as well as a new blob storage URL to indicate where you'd like the output log to be stored when it's created by the service.
 
 ### Import graph with Azure Digital Twins Explorer
 

articles/digital-twins/how-to-manage-model.md

@@ -88,7 +88,7 @@ To import models in bulk, you'll need to structure your models (and any other re
 
 [!INCLUDE [digital-twins-bulk-blob.md](../../includes/digital-twins-bulk-blob.md)]
 
-Then, the file can be used in an [Jobs API](/rest/api/digital-twins/dataplane/import-jobs) call.
+Then, the file can be used in an [Jobs API](/rest/api/digital-twins/dataplane/import-jobs) call. You'll provide the blob storage URL of the input file, as well as a new blob storage URL to indicate where you'd like the output log to be stored when it's created by the service.
 
 ## Retrieve models
 

articles/digital-twins/how-to-manage-twin.md

@@ -93,7 +93,7 @@ You can view an example import file and a sample project for creating these file
 
 [!INCLUDE [digital-twins-bulk-blob.md](../../includes/digital-twins-bulk-blob.md)]
 
-Then, the file can be used in an [Jobs API](/rest/api/digital-twins/dataplane/import-jobs) call.
+Then, the file can be used in an [Jobs API](/rest/api/digital-twins/dataplane/import-jobs) call. You'll provide the blob storage URL of the input file, as well as a new blob storage URL to indicate where you'd like the output log to be stored when it's created by the service.
 
 ## Get data for a digital twin
 

includes/digital-twins-bulk-blob.md

@@ -9,9 +9,6 @@ ms.author: baanders
 
 Next, the file needs to be uploaded into an append blob in [Azure Blob Storage](../articles/storage/blobs/storage-blobs-introduction.md). For instructions on how to create an Azure storage container, see [Create a container](../articles/storage/blobs/storage-quickstart-blobs-portal.md#create-a-container). Then, upload the file using your preferred upload method (some options are the [AzCopy command](../articles/storage/common/storage-use-azcopy-blobs-upload.md), the [Azure CLI](../articles/storage/blobs/storage-quickstart-blobs-cli.md#upload-a-blob), or the [Azure portal](https://portal.azure.com)).
 
->[!IMPORTANT]
-> The Azure Blob Storage container must have an **Append** blob type, so that the bulk import job can write to output logs.
-
 Once the NDJSON file has been uploaded to the container, get its **URL** within the blob container. You'll use this value later in the body of the bulk import API call.
 
 Here's a screenshot showing the URL value of a blob file in the Azure portal: