Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into tamram23-0330

Author: tamram

articles/app-service/includes/quickstart-java/quickstart-java-linux-maven-pivot.md

@@ -42,7 +42,7 @@ If Maven isn't your preferred development tool, check out our similar tutorials
 Clone the [sample project](https://github.com/Azure-Samples/app-service-java-quickstart) and check out the source code that runs with this version of the article.
 
 > [!TIP]
-> Though App Service supports older versions of Java, the sample project uses Java records and requires **Java 17**. For more information about Java records, see [JEP 395](https://openjdk.org/jeps/395).
+> Though App Service supports older versions of Java, the `booty-duke-app-service` sample project uses Java records and requires **Java 17**. For more information about Java records, see [JEP 395](https://openjdk.org/jeps/395).
 
 ```azurecli-interactive
 git clone https://github.com/Azure-Samples/app-service-java-quickstart
@@ -83,11 +83,14 @@ git clone https://github.com/Azure-Samples/app-service-java-quickstart
 
 Change directory to the completed project and build from the top level. Then `cd` to the subdirectory for petstore.
 
+> [!TIP]
+> The `petstore-ee7` sample requires **Java 11 or newer**. The `booty-duke-app-service` sample project requires **Java 17**. If your installed version of Java is less than 17, run the build from within the `petstore-ee7` directory, rather than at the top level.
+
 ```azurecli-interactive
 cd app-service-java-quickstart
 git checkout 20230308
-mvn clean install
 cd petstore-ee7
+mvn clean install
 ```
 
 ---

articles/app-service/overview-name-resolution.md

@@ -3,7 +3,7 @@ title: Name resolution in App Service
 description: Overview of how name resolution (DNS) works for your app in Azure App Service.
 author: madsd
 ms.topic: conceptual
-ms.date: 03/01/2023
+ms.date: 04/03/2023
 ms.author: madsd
 ---
 
@@ -35,15 +35,15 @@ Using the app setting `WEBSITE_DNS_ALT_SERVER`, you append a DNS server to end o
 
 If you require fine-grained control over name resolution, App Service allows you to modify the default behavior. You can modify retry attempts, retry timeout and cache timeout. Changing behavior like disabling or lowering cache duration may influence performance.
 
-|Property name|Default value|Allowed values|Description|
-|-|-|-|
-|dnsRetryAttemptCount|1|1-5|Defines the number of attempts to resolve where one means no retries|
-|dnsMaxCacheTimeout|30|0-60|Cache timeout defined in seconds. Setting cache to zero means you've disabled caching|
-|dnsRetryAttemptTimeout|3|1-30|Timeout before retrying or failing. Timeout also defines the time to wait for secondary server results if the primary doesn't respond|
+|Property name|Windows default value|Linux default value|Allowed values|Description|
+|-|-|-|-|
+|dnsRetryAttemptCount|1|5|1-5|Defines the number of attempts to resolve where one means no retries.|
+|dnsMaxCacheTimeout|30|0|0-60|Cache timeout defined in seconds. Setting cache to zero means you've disabled caching.|
+|dnsRetryAttemptTimeout|3|1|1-30|Timeout before retrying or failing. Timeout also defines the time to wait for secondary server results if the primary doesn't respond.|
 
 >[!NOTE]
-> * Changing name resolution behavior is not supported on Windows Container apps
-> * To enable DNS caching on Web App for Containers and Linux-based apps you must add the app setting `WEBSITE_ENABLE_DNS_CACHE`
+> * Changing name resolution behavior is not supported on Windows Container apps.
+> * To enable DNS caching on Web App for Containers and Linux-based apps, you must add the app setting `WEBSITE_ENABLE_DNS_CACHE`. This setting defaults to 30 seconds.
 
 Configure the name resolution behavior by using these CLI commands:
 
@@ -63,4 +63,4 @@ az resource show --resource-group <group-name> --name <app-name> --query propert
 
 - [Configure virtual network integration](./configure-vnet-integration-enable.md)
 - [Name resolution for resources in Azure virtual networks](../virtual-network/virtual-networks-name-resolution-for-vms-and-role-instances.md)
-- [General networking overview](./networking-features.md)
+- [General networking overview](./networking-features.md)

articles/azure-cache-for-redis/cache-best-practices-development.md

@@ -62,7 +62,7 @@ Some Redis operations, like the [KEYS](https://redis.io/commands/keys) command,
 
 ## Choose an appropriate tier
 
-Use Standard or Premium tier for production systems.  Don't use the Basic tier in production. The Basic tier is a single node system with no data replication and no SLA. Also, use at least a C1 cache. C0 caches are only meant for simple dev/test scenarios because:
+Use Standard, Premium, Enterprise, or Enterprise Flash tiers for production systems.  Don't use the Basic tier in production. The Basic tier is a single node system with no data replication and no SLA. Also, use at least a C1 cache. C0 caches are only meant for simple dev/test scenarios because:
 
 - they share a CPU core
 - use little memory
@@ -89,6 +89,10 @@ The public IP address assigned to your cache can change as a result of a scale o
 
 The default version of Redis that is used when creating a cache can change over time. Azure Cache for Redis might adopt a new version when a new version of open-source Redis is released. If you need a specific version of Redis for your application, we recommend choosing the Redis version explicitly when you create the cache.
 
+## Specific guidance for the Enterprise tiers
+
+Because the _Enterprise_ and _Enterprise Flash_ tiers are built on Redis Enterprise rather than open-source Redis, there are some differences in development best practices. See [Best Practices for the Enterprise and Enterprise Flash tiers](cache-best-practices-enterprise-tiers.md) for more information.
+
 ## Use TLS encryption
 
 Azure Cache for Redis requires TLS encrypted communications by default. TLS versions 1.0, 1.1 and 1.2 are currently supported. However, TLS 1.0 and 1.1 are on a path to deprecation industry-wide, so use TLS 1.2 if at all possible.
@@ -149,7 +153,7 @@ If your application validates certificate in code, you need to modify it to reco
 
 For more information, see [Client libraries](cache-best-practices-client-libraries.md#client-libraries).
 
-## Next steps
+## Next steps  
 
 - [Performance testing](cache-best-practices-performance.md)
 - [Failover and patching for Azure Cache for Redis](cache-failover.md)

articles/container-apps/workload-profiles-overview.md

@@ -68,6 +68,10 @@ You can constrain the memory and CPU usage of each app inside a workload profile
 
 When demand for new apps or more replicas of an existing app exceeds the profile's current resources, profile instances may be added. Inversely, if the number of apps or replicas goes down, profile instances may be removed. You have control over the constraints on the minimum and maximum number of profile instances. Azure calculates [billing](billing.md#consumption-dedicated) largely based on the number of running profile instances.
 
+## Networking
+
+When using workload profiles in the Consumption + Dedicated plan structure, additional networking features to fully secure your ingress/egress networking traffic such as user defined routes are available. To learn more about what networking features are supported, see [networking concepts](./networking.md), and for steps on how to secure your network with Container Apps, see the [lock down your Container App environment section](./networking.md#lock-down-your-container-app-environment).
+
 ## Next steps
 
 > [!div class="nextstepaction"]

articles/cosmos-db/mongodb/vcore/tutorial-nodejs-web-app.md

@@ -45,7 +45,7 @@ For the most straightforward dev environment, we use GitHub Codespaces so that y
 1. Create a new GitHub Codespace on the `main` branch of the [`azure-samples/msdocs-azure-cosmos-db-mongodb-mern-web-app`](https://github.com/azure-samples/msdocs-azure-cosmos-db-mongodb-mern-web-app) GitHub repository.
 
     > [!div class="nextstepaction"]
-    > [Open this project in GitHub Codespaces](https://github.com/azure-samples/msdocs-azure-cosmos-db-mongodb-mern-web-app/codespaces)
+    > [Open this project in GitHub Codespaces](https://github.com/codespaces/new?hide_repo_select=true&ref=main&repo=611024069)
 
 1. Wait for the Codespace to start. This startup process can take two to three minutes.
 
@@ -165,13 +165,13 @@ Start by running the sample application's API with the local MongoDB container t
     > [!NOTE]
     > The object ids (`_id`) are randomnly generated and will differ from this truncated example output.
 
-1. In the **client/** directory, create a new **.env** file.
+1. In the **server/** directory, create a new **.env** file.
 
-1. In the **client/.env** file, add an environment variable for this value:
+1. In the **server/.env** file, add an environment variable for this value:
 
     | Environment Variable | Value |
     | --- | --- |
-    | `CONNECTION_STRING` | The connection string to the Azure Cosmos DB for MongoDB vCore cluster. For now, use `mongodb://localhost`. |
+    | `CONNECTION_STRING` | The connection string to the Azure Cosmos DB for MongoDB vCore cluster. For now, use `mongodb://localhost:27017?directConnection=true`. |
 
     ```env
     CONNECTION_STRING=mongodb://localhost:27017?directConnection=true
@@ -270,8 +270,13 @@ Now, let's validate that the application works seamlessly with Azure Cosmos DB f
     ```shell
     exit
     ```
+1. In the **client/** directory, create a new **.env** file.
 
-1. Open the **client/.env** file again. Then, update the value of the `CONNECTION_STRING` environment variables with the connection string you used with the mongo shell:
+1. In the **client/.env** file, add an environment variable for this value:
+
+    | Environment Variable | Value |
+    | --- | --- |
+    | `CONNECTION_STRING` | The connection string to the Azure Cosmos DB for MongoDB vCore cluster. Use the same connection string you used with the mongo shell:
 
     ```output
     CONNECTION_STRING=<your-connection-string>