Merge pull request #250426 from mumian/0906-stack-new-warning

remove the new stack warning message

Author: prmerger-automator[bot]

articles/azure-resource-manager/bicep/deployment-stacks.md

@@ -3,7 +3,7 @@ title: Create & deploy deployment stacks in Bicep
 description: Describes how to create deployment stacks in Bicep.
 ms.topic: conceptual
 ms.custom: devx-track-azurecli, devx-track-azurepowershell, devx-track-bicep
-ms.date: 08/07/2023
+ms.date: 09/06/2023
 ---
 
 # Deployment stacks (Preview)
@@ -41,9 +41,6 @@ Deployment stacks provide the following benefits:
 
 ## Create deployment stacks
 
-> [!WARNING]
-> The `New-Az*DeploymentStack` cmdlets are incorrectly outputting a warning message regarding the current existence of a stack with the same name as the stack attempting to be created. When the stack exists, the warning message is not shown, which could lead to unintended upsert behavior. Conversely, if the stack doesn't exist, the cmdlets display a warning message, suggesting that the stack exists and requiring user interaction to proceed with the upsert. This behavior will be reversed soon with an upcoming change. In the interim, you can use the `-Force` flag when executing the cmdlets to bypass the warning prompt in case the stack doesn't exist. This way, you can proceed with the upsert process without user intervention.
-
 A deployment stack resource can be created at resource group, subscription, or management group scope. The template passed into a deployment stack defines the resources to be created or updated at the target scope specified for the template deployment.
 
 - A stack at resource group scope can deploy the template passed-in to the same resource group scope where the deployment stack exists.