Merge pull request #10299 from MicrosoftDocs/main638555654952899345sync_temp

For protected branch, push strategy should use PR and merge to target branch method to work around git push error

Author: learn-build-service-prod[bot]

docs/azure/end-to-end-deployment-entity-framework-core-github-actions.md

@@ -115,7 +115,7 @@ The publishing features of Visual Studio can handle creating these resources for
         - Select **Ok** to close the container apps environment dialog.
     - Select **Create** to close the original container apps dialog. Visual Studio creates the container app resource in Azure.
 1. Once the resource is created, make sure it's selected in the list of container apps, and then select **Next**.
-1. You'll need to create an Azure container registry to store the published image artifact for your app. Select the green **+** icon on the Container Registry screen.
+1. You'll need to create an Azure container registry to store the published image artifact for your app. Select the green **+** icon on the **Container Registry** screen.
 
     :::image type="content" source="./media/end-to-end-deployment-entity-framework-core-github-actions/visual-studio-container-registry.png" lightbox="./media/end-to-end-deployment-entity-framework-core-github-actions/visual-studio-container-registry-large.png" alt-text="A screenshot showing how to create a new container registry.":::
 

docs/azure/how-to-sign-in-with-azure-subscription.md

@@ -4,13 +4,13 @@ description: Sign in to Visual Studio for Windows with an Azure subscription and
 author: ghogen
 ms.subservice: azure-development
 ms.author: ghogen
+ms.date: 06/12/2024
 ms.topic: how-to
-ms.date: 10/19/2021
 ---
 
 # Sign in with an Azure subscription
 
-If you are not already signed in with an Azure subscription, you might encounter a dialog like the following ones.
+If you are not already signed in with an Azure subscription, you might encounter a dialog like these:
 
 ![Screenshot showing sign-in for Connected Services.](./media/sign-in-required-connected-services.png)
 
@@ -20,5 +20,25 @@ If you have a Visual Studio subscription, you already have an Azure subscription
 
 Visual Studio also gives you the opportunity to [create a new, free Azure account](https://signup.azure.com/signup?offer=Azure_MSDN) to try things out with.
 
+Visual Studio allows you to sign in with multiple accounts and it let's you work with Azure resources across multiple Azure subscriptions so no need to sign-out of one in order to sign-in with another!
+
 > [!NOTE]
-> Visual Studio allows you to sign in with multiple accounts and it let's you work with Azure resources across multiple Azure subscriptions so no need to sign-out of one in order to sign-in with another!
+> For Azure CLI users, be aware that the sign-in from Azure CLI is separate from the sign-in used in Visual Studio, so even if you're signed in to Azure by using `az login` on the same machine where you're running Visual Studio, you still need to provide credentials within Visual Studio.
+
+## To sign in to Azure from a dialog or wizard screen
+
+1. Select the **Sign In** button, and then choose **Add an account**. You should see options such as **Microsoft Work, school, or personal account**. This option means Microsoft Entra ID (Microsoft Account).
+
+   ![Screenshot of sign-in dropdown.](./media/sign-in-required-microsoft.png)
+
+1. Next, you see a screen listing Microsoft Accounts. Choose the account that has access to the Azure resources you require. Accounts known to Visual Studio are shown, but you can add another if the account you're looking for is not listed.
+
+1. Once you choose an account, you might be asked for credentials and two-factor authentication, depending on the security environment on your computer and your account's security settings.
+
+1. After a successful sign-in, focus returns to the dialog, and you should see your subscription listed in the place where the **Sign In** box was previously.
+
+To avoid having to sign in when you connect to an Azure service or publish to Azure, you can use Visual Studio's account management features to add your Azure subscription to your Visual Studio accounts. In that case, you are automatically signed in whenever you're using Visual Studio. See [Add and switch user accounts to Visual Studio](../ide/signing-in-to-visual-studio.md#add-and-switch-user-accounts-in-visual-studio).
+
+## Related content
+
+- [Sign in to Visual Studio with accounts that require multifactor authentication (MFA)](../ide/work-with-multi-factor-authentication.md)

docs/azure/media/sign-in-required-connected-services.png

@@ -25,7 +25,7 @@ In Visual Studio 2019 and earlier, you can also use Cloud Explorer to view and m
 > [!IMPORTANT]
 > Cloud Explorer has been retired in Visual Studio 2022. Instead, you can use the following alternatives:
 >
-> - To debug Azure App Services or Azure function apps, you can use the Connected Services or the Publish features available on all projects.
+> - To debug Azure App Services or Azure Functions apps, you can use the Connected Services or the Publish features available on all projects.
 >   - If you rely on Visual Studio for publishing, you can access this feature under the "Additional Options" in the Hosting section.
 >   - If you don't use the publishing feature, the [Connected Services](overview-connected-services.md?view=vs-2022&preserve-view=true) node inside each Project in your Solution can help you configure access to Azure resources and invoke various operations like remote debugging, remote profiling, starting/stopping the application, view streaming logs, and more.
 > - Use [Microsoft Azure Storage Explorer](/azure/vs-azure-tools-storage-manage-with-storage-explorer) is a free, standalone app from Microsoft. You can use it to work visually with Azure Storage data on Windows, macOS, and Linux.

docs/azure/media/sign-in-required-microsoft.png

@@ -40,7 +40,7 @@ Use one of the following formats to specify a rule in the **FxCopCmd.exe /RuleId
 
 In Visual Studio Code analysis, rules can be specified by using the CodeAnalysisRules property of MSBuild with the following format:
 
-**\<CodeAnalysisRules>-**{*Category*&#124;*Namespace*}#*RuleId*[**;**...]**\</CodeAnalysisRules>**
+`<CodeAnalysisRules>-{Category&#124;Namespace}#RuleId[;...]</CodeAnalysisRules>`
 
 For example