Fix broken links - Architecture and Azure

docs/architecture/containerized-lifecycle/design-develop-containerized-apps/visual-studio-tools-for-docker.md

@@ -79,9 +79,9 @@ The following table might help you decide how to set these options.
 > [!TIP]
 > For further details on the services implementation and use of Visual Studio Tools for Docker, read the following articles:
 >
-> Debug apps in a local Docker container: <https://docs.microsoft.com/azure/vs-azure-tools-docker-edit-and-refresh>
+> Debug apps in a local Docker container: <https://docs.microsoft.com/visualstudio/containers/edit-and-refresh>
 >
-> Deploy an ASP.NET container to a container registry using Visual Studio: <https://docs.microsoft.com/azure/vs-azure-tools-docker-hosting-web-apps-in-docker>
+> Deploy an ASP.NET container to a container registry using Visual Studio: <https://docs.microsoft.com/visualstudio/containers/hosting-web-apps-in-docker>
 
 > [!div class="step-by-step"]
 > [Previous](docker-apps-inner-loop-workflow.md)

docs/architecture/microservices/architect-microservice-container-applications/asynchronous-message-based-communication.md

@@ -79,7 +79,7 @@ Additional topics to consider when using asynchronous communication are message
 ## Additional resources
 
 - **Event Driven Messaging** \
-  <https://soapatterns.org/design_patterns/event_driven_messaging>
+  <https://patterns.arcitura.com/soa-patterns/design_patterns/event_driven_messaging>
 
 - **Publish/Subscribe Channel** \
   <https://www.enterpriseintegrationpatterns.com/patterns/messaging/PublishSubscribeChannel.html>

docs/architecture/microservices/docker-application-development-process/docker-app-development-workflow.md

@@ -447,7 +447,7 @@ The above command will create a new container instance from the specified image,
 
 In this case, the command binds the internal port 5000 of the container to port 80 of the host machine. This means that the host is listening on port 80 and forwarding to port 5000 on the container.
 
-The hash shown is the container ID and it’s also assigned a random readable name if the `--name` option is not used.
+The hash shown is the container ID and it's also assigned a random readable name if the `--name` option is not used.
 
 #### Using Visual Studio
 
@@ -490,7 +490,7 @@ The important point here is that, as shown in Figure 5-12, in Visual Studio 2019
 ### Additional resources
 
 - **Deploy an ASP.NET container to a remote Docker host** \
-  <https://docs.microsoft.com/azure/vs-azure-tools-docker-hosting-web-apps-in-docker>
+  <https://docs.microsoft.com/visualstudio/containers/hosting-web-apps-in-docker>
 
 ### A note about testing and deploying with orchestrators
 

docs/architecture/microservices/secure-net-microservices-web-applications/azure-key-vault-protects-secrets.md

@@ -42,8 +42,8 @@ The **Microsoft.Extensions.Configuration.AzureKeyVault** package allows an ASP.N
 - **Data Protection key management and lifetime in ASP.NET Core** \
   [https://docs.microsoft.com/aspnet/core/security/data-protection/configuration/default-settings](/aspnet/core/security/data-protection/configuration/default-settings)
 
-- **Microsoft.Extensions.Configuration.KeyPerFile** GitHub repository. \
-  </~https://github.com/dotnet/extensions/tree/master/src/Configuration/Config.KeyPerFile>
+- **Microsoft.Extensions.Configuration** GitHub repository. \
+  </~https://github.com/dotnet/extensions/tree/master/src/Configuration>
 
 >[!div class="step-by-step"]
 >[Previous](developer-app-secrets-storage.md)

docs/architecture/modern-web-apps-azure/work-with-data-in-asp-net-core-apps.md

@@ -367,7 +367,7 @@ In addition to relational and NoSQL storage options, ASP.NET Core applications c
 **References – Azure Storage**
 
 - Azure Storage Introduction
-  <https://docs.microsoft.com/azure/storage/storage-introduction>
+  <https://docs.microsoft.com/azure/storage/common/storage-introduction>
 
 ## Caching