Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit 8eafafc

Browse files
authoredOct 17, 2024
Doc updates (#261)
- Typos - Updates for consistency - Updated diagram on prod deployment doc - Adds troubleshooting tip for MFA tenants
1 parent 2206ac6 commit 8eafafc

File tree

7 files changed

+31
-374
lines changed

7 files changed

+31
-374
lines changed
 

‎README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
1-
# Modern web app pattern for .NET
1+
# Modern Web App pattern for .NET
22

3-
The reference implementation provides a production-grade web application that uses best practices from our guidance and gives developers concrete examples to build their own Modern Web Application in Azure. This repository specifically demonstrates a concert ticketing application for the fictional company Relecloud, embodying the modern web app pattern with a focus on .NET technologies. It guides developers through a simulated migration from an on-premises ASP.NET application to Azure, detailing the architectural changes and enhancements that capitalize on the cloud's strengths during the initial adoption phase.
3+
The reference implementation provides a production-grade web application that uses best practices from our guidance and gives developers concrete examples to build their own Modern Web App in Azure. This repository specifically demonstrates a concert ticketing application for the fictional company Relecloud, embodying the Modern Web App pattern with a focus on .NET technologies. It guides developers through a simulated migration from an on-premises ASP.NET application to Azure, detailing the architectural changes and enhancements that capitalize on the cloud's strengths during the initial adoption phase.
44

5-
This project has [a companion article in the Azure Architecture Center](https://aka.ms/eap/mwa/dotnet/doc) that describes design patterns and best practices <!--and [a six-part video series (YouTube)](https://aka.ms/eap/mwa/dotnet/videos) that details the modern web app pattern for .NET web app -->. Here's an outline of the contents in this readme:
5+
This project has [a companion article in the Azure Architecture Center](https://aka.ms/eap/mwa/dotnet/doc) that describes design patterns and best practices. Here's an outline of the contents in this readme:
66

77
- [Architecture](#architecture)
88
- [Workflow](#workflow)

‎guide/apply-the-pattern.md

Lines changed: 0 additions & 191 deletions
This file was deleted.

‎guide/mwa-overview.md

Lines changed: 0 additions & 11 deletions
This file was deleted.

‎guide/plan-the-implementation.md

Lines changed: 0 additions & 165 deletions
This file was deleted.

‎infra/main.bicep

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@ targetScope = 'subscription'
22

33
// ========================================================================
44
//
5-
// Relecloud Scenario of the Modern Web Application (MWA)
5+
// Relecloud Scenario of the Modern Web App (MWA)
66
// Infrastructure description
77
// Copyright (C) 2023 Microsoft, Inc.
88
//

‎prod-deployment.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
# Steps to deploy the production deployment
2-
This section describes the deployment steps for the reference implementation of a modern web application pattern with .NET on Microsoft Azure. These steps guide you through using the jump box that is deployed when performing a network isolated deployment because access to resources will be restricted from public network access and must be performed from a machine connected to the vnet.
2+
This section describes the deployment steps for the reference implementation of a Modern Web App pattern with .NET on Microsoft Azure. These steps guide you through using the jump box that is deployed when performing a network isolated deployment because access to resources will be restricted from public network access and must be performed from a machine connected to the vnet.
33

4-
![Diagram showing the network focused architecture of the reference implementation.](./assets/images/mwa-architecture.png)
4+
![Diagram showing the architecture of the MWA implementation.](./assets/icons/modern-web-app-dotnet.svg)
55

66
## Prerequisites
77

‎troubleshooting.md

Lines changed: 25 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -97,4 +97,28 @@ When the `azd provision` command runs it creates a deployment resource in your s
9797
az deployment sub delete -n <deployment-name>
9898
```
9999
100-
1. You should now be able to run the `azd provision` command and resume your deployment.
100+
1. You should now be able to run the `azd provision` command and resume your deployment.
101+
102+
## ERROR: reauthentication required, run `azd auth login --scope https://management.azure.com//.default` to log in
103+
This error can happen when you are using an account that has access to multiple subscriptions. The `azd auth` command is not able to retrieve a list of the subscriptions that you can access when that tenant is configured to require a Multi-Factor Auth experience that was not completed.
104+
105+
**Alternate error message text**
106+
107+
Depending on your workflow you may get a different error message for the same issue:
108+
109+
```sh
110+
ERROR: resolving bicep parameters file: fetching current principal id: getting tenant id for subscription...
111+
```
112+
113+
### Workaround
114+
You should complete the MFA experience for your default tenant, and the tenant that you wish to access by running both authentication commands:
115+
116+
1. Authenticate to your default tenant
117+
```sh
118+
azd auth login --use-device-code
119+
```
120+
121+
1. Authenticate to the tenant that owns the subscription you want to use
122+
```sh
123+
azd auth login --use-device-code --tenant <tenant-id>
124+
```

0 commit comments

Comments
 (0)
Please sign in to comment.