On branch dd-2275862 Copyeding. Please take out of DRAFT state.

modified:   articles/storage/blobs/TOC.yml

- Differentiate between Java SE, Spring Boot and Quarkus as flavors of what Microsoft thnks of as "Java".

modified:   articles/storage/blobs/storage-quickstart-blobs-java-quarkus.md

- Declare dependency on Azure CLI.

- Warn about using local file storage.

- Add **Clean up** section.

- Add **Next steps** links to deploy the app the reader just created.

modified:   articles/storage/blobs/storage-quickstart-blobs-java.md

- Clarify that this article applies to Java SE. The other two articles, about Spring and Quarkus, also apply to Java. Therefore, this article became incorrectly named as soon as an article about Spring was added. It became even more incorrectly named when an artile about Quarkus was adde. All three articles are about Java.

modified:   includes/assign-roles.md

- Include a link to Storage Blob Data Contributor reading.

Signed-off-by: Ed Burns <[email protected]>

Author: edburns

articles/storage/blobs/TOC.yml

@@ -34,9 +34,9 @@ items:
       href: storage-quickstart-blobs-dotnet.md
     - name: Java
       items:
-      - name: Java
+      - name: Java SE
         href: storage-quickstart-blobs-java.md
-      - name: Spring
+      - name: Spring Boot
         href: /azure/developer/java/spring-framework/configure-spring-boot-starter-java-app-with-azure-storage?toc=/azure/storage/blobs/toc.json
       - name: Quarkus
         href: storage-quickstart-blobs-java-quarkus.md

articles/storage/blobs/storage-quickstart-blobs-java-quarkus.md

@@ -18,10 +18,11 @@ Get started with the Quarkus extension for Azure Blob Storage to manage blobs an
 
 ## Prerequisites
 
-- Azure account with an active subscription - [create an account for free](https://azure.microsoft.com/free/?ref=microsoft.com&utm_source=microsoft.com&utm_medium=docs&utm_campaign=visualstudio)
+- Azure account with an active subscription - [create an account for free](https://azure.microsoft.com/free/?ref=microsoft.com&utm_source=microsoft.com&utm_medium=docs&utm_campaign=visualstudio).
+- Azure CLI - [Install the Azure CLI](/cli/azure/install-azure-cli) 2.62.0 or above to run Azure CLI commands.
 - Azure Storage account - [create a storage account](../common/storage-account-create.md).
-- [Java Development Kit (JDK)](/java/azure/jdk/) version 17 or above
-- [Apache Maven](https://maven.apache.org/download.cgi)
+- [Java Development Kit (JDK)](/java/azure/jdk/) version 17 or above.
+- [Apache Maven](https://maven.apache.org/download.cgi).
 
 ## Setting up
 
@@ -81,13 +82,13 @@ You can authorize access to data in your storage account using the following ste
 
 The code example performs the following actions:
 
-- Injects a client object that is already authorized for data access via `DefaultAzureCredential` using the Quarkus extension for Azure Blob Storage
-- Creates a container in a storage account
-- Uploads a blob to the container
-- Lists the blobs in the container
-- Downloads the blob data to the local file system
-- Deletes the blob and container resources created by the app
-- Deleting the local source and downloaded files
+- Injects a client object that is already authorized for data access via `DefaultAzureCredential` using the Quarkus extension for Azure Blob Storage.
+- Creates a container in a storage account.
+- Uploads a blob to the container.
+- Lists the blobs in the container.
+- Downloads the blob data to the local file system.
+- Deletes the blob and container resources created by the app.
+- Deleting the local source and downloaded files.
 
 Run the application in JVM mode using the following command:
 
@@ -186,7 +187,10 @@ This is all you need to code to get a client object using the Quarkus extension
 
 ### Manage blobs and containers
 
-The following code snippet shows how to create a container, upload a blob, list blobs in a container, and download a blob:
+The following code snippet shows how to create a container, upload a blob, list blobs in a container, and download a blob.
+
+> [!NOTE]
+> Writing to the local filesystem is considered a bad practice in cloud native applications. However, the sample uses the local filesystem to illustrate the use of blob storage in a way that is easy to for the user to verify. If taking an application to production, review your storage options and choose the best option for your needs. See [Review your storage options](/azure/architecture/guide/technology-choices/storage-options).
 
 ```java
 // Create a unique name for the container
@@ -262,7 +266,13 @@ These operations are similar to the [Quickstart: Azure Blob Storage client libra
 - [Download blobs](storage-quickstart-blobs-java.md#download-blobs)
 - [Delete a container](storage-quickstart-blobs-java.md#delete-a-container)
 
-## Next step
+## Clean up
+
+You can choose to follow the links in the **Next steps** section to deploy the Quarkus application to Azure. Or you can clean up the storage account by deleting the resource group. For more information, see [Azure Resource Manager resource group and resource deletion](/azure/azure-resource-manager/management/delete-resource-group).
+
+## Next steps
 
 > [!div class="nextstepaction"]
 > [Azure Storage samples and developer guides for Java](../common/storage-samples-java.md?toc=/azure/storage/blobs/toc.json)
+> [Deploy a Java application with Quarkus on an Azure Kubernetes Service cluster](/azure/aks/howto-deploy-java-quarkus-app)
+> [Deploy a Java application with Quarkus on Azure Container Apps](https://learn.microsoft.com/en-us/azure/developer/java/ee/deploy-java-quarkus-app)

articles/storage/blobs/storage-quickstart-blobs-java.md

@@ -11,7 +11,7 @@ ms.devlang: java
 zone_pivot_groups: azure-blob-storage-quickstart-options
 ---
 
-# Quickstart: Azure Blob Storage client library for Java
+# Quickstart: Azure Blob Storage client library for Java SE
 
 ::: zone pivot="blob-storage-quickstart-scratch"
 
@@ -612,3 +612,6 @@ You'll be prompted to confirm the deletion of the resources. Enter `y` to confir
 
 > [!div class="nextstepaction"]
 > [Azure Storage samples and developer guides for Java](../common/storage-samples-java.md?toc=/azure/storage/blobs/toc.json)
+> [Azure Storage samples and developer guides for Java](../common/storage-samples-java.md?toc=/azure/storage/blobs/toc.json)
+> [Quickstart: Quarkus extension for Azure Blob Storage](storage-quickstart-blobs-java-quarkus)
+> [Use Spring Boot to upload a file to Azure Blob Storage](/azure/developer/java/spring-framework/configure-spring-boot-starter-java-app-with-azure-storage?toc=/azure/storage/blobs/toc.json)

includes/assign-roles.md

@@ -10,7 +10,7 @@ ms.author: alexwolf
 ms.custom: include file
 ---
 
-When developing locally, make sure that the user account that is accessing blob data has the correct permissions. You'll need **Storage Blob Data Contributor** to read and write blob data. To assign yourself this role, you'll need to be assigned the **User Access Administrator** role, or another role that includes the **Microsoft.Authorization/roleAssignments/write** action. You can assign Azure RBAC roles to a user using the Azure portal, Azure CLI, or Azure PowerShell. You can learn more about the available scopes for role assignments on the [scope overview](../articles/role-based-access-control/scope-overview.md) page.
+When developing locally, make sure that the user account that is accessing blob data has the correct permissions. You'll need **Storage Blob Data Contributor** to read and write blob data. To assign yourself this role, you'll need to be assigned the **User Access Administrator** role, or another role that includes the **Microsoft.Authorization/roleAssignments/write** action. You can assign Azure RBAC roles to a user using the Azure portal, Azure CLI, or Azure PowerShell. You can learn more about the Storage Blob Data Contributor role in [Storage Blob Data Contributor](/azure/role-based-access-control/built-in-roles/storage#storage-blob-data-contributor).  You can learn more about the available scopes for role assignments on the [scope overview](../articles/role-based-access-control/scope-overview.md) page.
 
 In this scenario, you'll assign permissions to your user account, scoped to the storage account, to follow the [Principle of Least Privilege](../articles/active-directory/develop/secure-least-privileged-access.md). This practice gives users only the minimum permissions needed and creates more secure production environments.