Use clear visuals for Alerts (#80)

* Change Readme to correct Alert visuals
* Update challenge 1 to use correct alert visuals
* Update challenge 2 to use correct alert visuals
* Update challenge 3 to use correct alert visuals
* Update challenge 4 to use correct alert visuals
* Update challenge 5 to use correct alert visuals
* fix typo in challenge 5
* Update challenge 6 to use correct alert visuals

03-Azure/01-03-Infrastructure/06_Migration_Datacenter_Modernization/Readme.md

@@ -107,9 +107,11 @@ The goal of this exercise is to...
 ### Actions
 
 * Create a Azure Migrate Project
-    - 💥 **To be able to create a Business Case, make sure to select Europe as the Geography for the Azure Migrate Project** 
+> [!IMPORTANT]
+> To be able to create a Business Case, make sure to select Europe as the Geography for the Azure Migrate Project
 * Deploy a Azure Migrate Appliance
-    - 💥 **Carefully select the appropriate OS for the Azure Migrate Appliance. Windows Server 2016 is officially supported. Windows Server 2019 will work as well. Windows Server 2022 does not work yet.**
+> [!IMPORTANT]
+> Carefully select the appropriate OS for the Azure Migrate Appliance. Windows Server 2016 is officially supported. Windows Server 2019 will work as well. Windows Server 2022 does not work yet.
 * Create a continuous discovery of your source environment
 
 ### Success criteria
@@ -159,7 +161,8 @@ The goal of this exercise is to create a business case. The Business case capabi
 - Quick wins for migration and modernization including end of support Windows OS and SQL versions.
 - Long term cost savings by moving from a capital expenditure model to an Operating expenditure model, by paying for only what you use.
 
-💥 **The Business case capability is currently in public preview** 
+> [!WARNING]
+> The Business case capability is currently in public preview
 
 ### Actions
 
@@ -277,9 +280,11 @@ The goal of this exercise is to ...
 * An migration has been performed towards PaaS instead of IaaS.
 * The App Services are accessible using the source Load Balancer.
 
-💥 **The new App Service migration capability is currently in public preview** 
+> [!WARNING]
+> The new App Service migration capability is currently in public preview
 
-💥 **For the current version (June 2023) of the App Service migration scripts, Basic Authentication on Azure Web Apps is a hard requirement. Make sure that no Azure Policy restrictions are in place that prohibit the use of Basic Authentication for Azure App Services**
+> [!IMPORTANT]
+> For the current version (June 2023) of the App Service migration scripts, Basic Authentication on Azure Web Apps is a hard requirement. Make sure that no Azure Policy restrictions are in place that prohibit the use of Basic Authentication for Azure App Services
 
 ### Learning resources
 * [App Service assessment overview](https://learn.microsoft.com/en-us/azure/migrate/concepts-azure-webapps-assessment-calculation)

03-Azure/01-03-Infrastructure/06_Migration_Datacenter_Modernization/walkthrough/challenge-1/solution.md

@@ -20,7 +20,8 @@ Duration: 30 minutes
 - Select a region
 - Wait for the deployment to finish
 
-💡 Please note that the deployment may take up to 10 minutes
+> [!NOTE]
+> Please note that the deployment may take up to 10 minutes
 
 ### **Task 2: Verify the deployed resources**
 The bicep deployment should have created the following resources

03-Azure/01-03-Infrastructure/06_Migration_Datacenter_Modernization/walkthrough/challenge-2/solution.md

@@ -32,7 +32,8 @@ Your previousley created Azure Migrate project should be preselected.
 
 To start physical server discovery you must install the Azure Migrate Appliance on your on-premises. The Azure Migrate Appliance can be downloaded as a OVA or VHD template or you can download a ZIP file containing a PowerShell script to install it on a already existing server. For the purpose of this MicroHack we will install the Azure Migrate Appliance via the PowerShell script on a Windows Server 2019 system.
 
-💡 Please make sure to check the [prerequisites](https://learn.microsoft.com/en-us/azure/migrate/tutorial-discover-physical#prerequisites) of the Azure Migrate Appliance.
+> [!IMPORTANT]
+> Please make sure to check the [prerequisites](https://learn.microsoft.com/en-us/azure/migrate/tutorial-discover-physical#prerequisites) of the Azure Migrate Appliance.
 
 In the Azure Portal select *Virtual machines* from the navigation pane on the left. Select *Create -> Azure virtual machine*
 
@@ -42,7 +43,8 @@ Under Basics select the *source-rg* Resource Group and provide a name for the se
 
 ![image](./img/AzMigApp2.png)
 
-💡 For the Username and Password you can either select a combination of your choice or check the secrets within the KeyVault.
+> [!NOTE]
+> For the Username and Password you can either select a combination of your choice or check the secrets within the KeyVault.
 
 Accept the default disk settings and click next to select the *Networking* tab. Select the *source-vnet* Virtual Network, select the *source-subnet* Subnet and make sure to select *None* for the Public IP and NIC network security group.
 
@@ -60,7 +62,9 @@ Select *Bastion* from the navigation pane on the left, provide the credentials t
 
 ![image](./img/AzMigApp6.png)
 
-💡 You can also select *Password from Azure KeyVault* under *Authentication Type* if you set the password during VM creation to match the secret stored in the KeyVault.
+> [!NOTE]
+> You can also select *Password from Azure KeyVault* under *Authentication Type* if you set the password during VM creation to match the secret stored in the KeyVault.
+
 
 ### **Task 3: Deploy the Azure Migrate Appliance**
 
@@ -103,7 +107,8 @@ Select Option 1 for *public endpoint* and confirm you selection to start the ins
 
 Select *N* for IE11 uninstallation. 
 
-💡 Please note the Warning that IE11 is incompatible with latest Azure Migrate Appliance configuration manager and make sure using Microsoft Edge to configure the Azure Migrate appliance
+> [!WARNING]
+> Please note the Warning that IE11 is incompatible with latest Azure Migrate Appliance configuration manager and make sure using Microsoft Edge to configure the Azure Migrate appliance
 
 ![image](./img/Discover8.png)
 
@@ -132,7 +137,8 @@ After successfull authentication, appliance will be registered with the Azure Mi
 Next you need to specify the credentials that will be used to connect to the source server for discovery.
 Add one entry for Windows and for Linux devices. The friendly name will be used later on when specifiying the individual systems.
 
-💡 For the Username and Password check the secrets within the KeyVault.
+> [!NOTE]
+> For the Username and Password check the secrets within the KeyVault.
 
 ![image](./img/Discover15.png)
 
@@ -150,7 +156,8 @@ After discovery has been successfully initiated, go to the Azure portal to revie
 
 You can click *Overview* to get more insights on what information were discovered.
 
-💡 If no inventory data is available, click Refresh to refresh inventory data.
+> [!NOTE]
+> If no inventory data is available, click Refresh to refresh inventory data.
 
 You successfully completed challenge 2! 🚀🚀🚀
 

03-Azure/01-03-Infrastructure/06_Migration_Datacenter_Modernization/walkthrough/challenge-3/solution.md

@@ -19,7 +19,8 @@ Provide a name for the business case and select a target location. For the migra
 
 Wait for the business case creation to complete and click on the business case name to open it.
 
-💡 Please note that business case creation can take up to 30 minutes.
+> [!NOTE]
+> Please note that business case creation can take up to 30 minutes.
 
 ![image](./img/bc3.png)
 

03-Azure/01-03-Infrastructure/06_Migration_Datacenter_Modernization/walkthrough/challenge-4/solution.md

@@ -49,7 +49,8 @@ Review your selection and click on *Create assessment*.
 
 ![image](./img/Assess9.png)
 
-💡 Please note that the computation of the assessment can take a few minutes.
+> [!NOTE]
+> Please note that the computation of the assessment can take a few minutes.
 
 When finished the assessment will show up with the status *Ready*.
 
@@ -67,7 +68,8 @@ The Azure VM assessment overview provides details about:
 * Monthly cost estimation: The estimated monthly compute and storage costs for running the VMs in Azure.
 * Monthly storage cost estimation: Estimated costs for disk storage after migration.
 
-💡 Please note that confidence rating for the assessment is marked as low. This is due to missing or to less performance data. It is recommended that you collect performance data via the Azure Migrate appliance at least on day before creating the assessment.
+> [!IMPORTANT]
+> Please note that confidence rating for the assessment is marked as low. This is due to missing or to less performance data. It is recommended that you collect performance data via the Azure Migrate appliance at least on day before creating the assessment..
 
 ![image](./img/Assess12.png)
 
@@ -128,7 +130,8 @@ Within the *Discovered servers* scrren click on *Refresh*. You should now be abl
 
 ![image](./img/Depend5.png)
 
-💡 Please note that it could take some time for the dependency data to show up. 
+> [!NOTE]
+> Please note that it could take some time for the dependency data to show up. 
 
 Once the dependency data has been uploaded to Azure Migrate, you should be able to show the different dependencies of the discovered servers.
 

03-Azure/01-03-Infrastructure/06_Migration_Datacenter_Modernization/walkthrough/challenge-5/solution.md

@@ -10,10 +10,12 @@ Please make sure thet you successfully completed [Challenge 4](../challenge-4/so
 
 To start physical server migration you must install the Azure Replication Appliance on your on-premises. The Azure Replication Appliance can be downloaded as a OVA template or you can download the appliance installer to install it on a already existing server. For the purpose of this MicroHack we will install the Azure Replication Appliance via the installer on a new Windows Server 2019 system.
 
-💡 Please make sure to check the [prerequisites](https://learn.microsoft.com/en-us/azure/migrate/migrate-replication-appliance) of the Azure 
+> [!IMPORTANT]
+> Please make sure to check the [prerequisites](https://learn.microsoft.com/en-us/azure/migrate/migrate-replication-appliance) of the Azure 
 Replication Appliance.
 
-💡 Please note that it is currently [not supported](https://learn.microsoft.com/en-us/azure/migrate/common-questions-appliance#can-the-azure-migrate-appliancereplication-appliance-connect-to-the-same-vcenter) to install the Azure Migrate Replication Appliance on the same system as the Azure Migrate Appliance.
+> [!IMPORTANT]
+> Please note that it is currently [not supported](https://learn.microsoft.com/en-us/azure/migrate/common-questions-appliance#can-the-azure-migrate-appliancereplication-appliance-connect-to-the-same-vcenter) to install the Azure Migrate Replication Appliance on the same system as the Azure Migrate Appliance.
 
 In the Azure Portal select *Virtual machines* from the navigation pane on the left. Select *Create -> Azure virtual machine*
 
@@ -23,7 +25,8 @@ Under Basics select the *source-rg* Resource Group and provide a name for the se
 
 ![image](./img/azreplapl2.png)
 
-💡 For the Username and Password you can either select a combination of your choice or check the secrets within the KeyVault.
+> [!NOTE]
+> For the Username and Password you can either select a combination of your choice or check the secrets within the KeyVault.
 
 Add an additional 1024GiB Standard HDD LRS data disk to the Virtual Machine and click *Next*
 
@@ -47,8 +50,8 @@ Select *Bastion* from the navigation pane on the left, provide the credentials t
 
 ![image](./img/azreplapl6.png)
 
-💡 You can also select *Password from Azure KeyVault* under *Authentication Type* if you set the password during VM creation to match the secret stored in the KeyVault.
-
+> [!NOTE]
+> You can also select *Password from Azure KeyVault* under *Authentication Type* if you set the password during VM creation to match the secret stored in the KeyVault.
 
 ### **Task 2: Setup the Azure Replication Appliance**
 
@@ -94,7 +97,8 @@ Review the prerequisites check of the installer. Note that you can safely ignore
 
 Specify the required passwords and note the password requirements. 
 
-💡 For the Passwords you can either select your choice or check the secrets within the KeyVault to reuse the password.
+> [!NOTE]
+> For the Username and Password you can either select a combination of your choice or check the secrets within the KeyVault.
 
 ![image](./img/mig10.png)
 
@@ -104,7 +108,8 @@ Select *No* for *Do you want to protect VMware virtual machines* and click *Next
 
 Verify the *Install location*. The installer should automatically pre-select the largest disk, in our case the 1024 GiB data disk that was created during VM creation.
 
-💡 The additional data disk needs to be initialized first using the [Windows Disk Management tool](https://learn.microsoft.com/en-us/windows-server/storage/disk-management/initialize-new-disks#initialize-a-new-disk)
+> [!IMPORTANT]
+> The additional data disk needs to be initialized first using the [Windows Disk Management tool](https://learn.microsoft.com/en-us/windows-server/storage/disk-management/initialize-new-disks#initialize-a-new-disk)
 
 ![image](./img/mig12.png)
 
@@ -155,7 +160,8 @@ To install the Mobility service agent on the Windows machines follow the followi
 
 ![image](./img/maw2.png)
 
-  * 💥 Don't regenerate the passphrase. This will break connectivity and you will have to reregister the replication appliance.
+> [!WARNING]
+> Don't regenerate the passphrase. This will break connectivity and you will have to reregister the replication appliance.
 
 #### **Task 3.1: Install the Mobility service on the Windows VMs**
 
@@ -171,8 +177,9 @@ cd C:\Temp\Extracted
 ```shell
 UnifiedAgent.exe /Role "MS" /Platform "VmWare" /Silent /CSType CSLegacy
 ```
-![image](./img/maw3-1.png)     
-💡 You need to specify *VmWare* for the *Platform* parameter also for physical servers.
+![image](./img/maw3-1.png)   
+> [!IMPORTANT]
+> You need to specify *VmWare* for the *Platform* parameter also for physical servers.
 
 3. Register the agent with the replication appliance:
 ```shell
@@ -182,7 +189,8 @@ UnifiedAgentConfigurator.exe /CSEndPoint \<replication appliance IP address\> /P
 ```
 ![image](./img/maw3-2.png)     
 
-**💥 Repeat the above steps for the second Windows Server**
+> [!IMPORTANT]
+> Repeat the above steps for the second Windows Server
 
 ### **Task 4: Enable Replication**
 
@@ -303,7 +311,8 @@ Under *Frontend IP configuration*, click *Add a frontend IP configuration* and c
 Under *Backend Pools*, select *Add a backend Pool*. Provide a name and select the *destination-vnet* as the Virtual Network.
 Add *10.2.1.4* and *10.2.1.5* as the IP addresses.
 
-💡 Please note: Azure reserves the first four addresses (0-3) in each subnet address range, and doesn't assign the addresses. Azure assigns the next available address to a resource from the subnet address range. So it is predictable which IP addresses will be assigned to the destination VMs after the migration.
+> [!NOTE]
+> Please note: Azure reserves the first four addresses (0-3) in each subnet address range, and doesn't assign the addresses. Azure assigns the next available address to a resource from the subnet address range. So it is predictable which IP addresses will be assigned to the destination VMs after the migration.
 
 ![image](./img/prep4.png)
 
@@ -340,7 +349,8 @@ Select *Endpoints* and click *Add*. Add each public IP of the source and destina
 
 ![image](./img/prep11.png)
 
-💡 Please note: To be able to add the public IP addresses they need to be configured with an [DNS name lable](https://learn.microsoft.com/en-us/azure/dns/dns-custom-domain?toc=%2Fazure%2Fvirtual-network%2Ftoc.json#public-ip-address).
+> [!NOTE]
+> Please note: To be able to add the public IP addresses they need to be configured with an [DNS name lable](https://learn.microsoft.com/en-us/azure/dns/dns-custom-domain?toc=%2Fazure%2Fvirtual-network%2Ftoc.json#public-ip-address).
 
 Check the Overview section under the navigation pane and note that the source load balancer is shown as *online* whereas the 
 destination load balancer is shown as *degraded*. If you copy the DNS name of the Traffic Manager profile and paste it into your browser, you should be able to browse the source web servers through the Traffic Manager Profile.
@@ -395,7 +405,8 @@ From the Traffic Manager Profile you can now also safley remove the endpoint for
 
 ![image](./img/finalmig10.png)
 
-💡 **Please note: Normaly it would be safe now to completley remove the *source-rg* Resource Group. However, we will reuse the source environment in [Challenge 6](https://github.com/microsoft/MicroHack/tree/MigrationModernizationMicroHack/03-Azure/01-03-Infrastructure/06_Migration_Datacentre_Modernization#challenge-6---modernize-with-azure) to see how Azure Migrate will help to modernize our infrastructure.**
+> [!WARNING]
+> **Please note: Normally it would be safe now to completley remove the *source-rg* Resource Group. However, we will reuse the source environment in [Challenge 6](https://github.com/microsoft/MicroHack/tree/MigrationModernizationMicroHack/03-Azure/01-03-Infrastructure/06_Migration_Datacentre_Modernization#challenge-6---modernize-with-azure) to see how Azure Migrate will help to modernize our infrastructure.**
 
 You successfully completed challenge 5! 🚀🚀🚀
 

03-Azure/01-03-Infrastructure/06_Migration_Datacenter_Modernization/walkthrough/challenge-6/solution.md

@@ -17,7 +17,9 @@ Azure App Service bulk migration capabilities are now in public preview through
 * Discover and migrate with Java Tomcat applications to App Service Linux and to Azure Kubernetes Service.
 * Containerize your ASP.NET web apps and move them to either Windows Containers on App Service or to Azure Kubernetes Service.
 
-**💥 Currently this feature has a few [limitations](https://learn.microsoft.com/en-us/azure/migrate/concepts-migration-webapps#limitations) and therefore it can't be used to migrate web apps directly from physical servers. However, we can use it at least to perform the assessment of our web apps and use the [App Service migration assistant tool](https://learn.microsoft.com/en-us/azure/app-service/app-service-asp-net-migration) for the migration.**
+> [!WARNING]
+> **Currently this feature has a few [limitations](https://learn.microsoft.com/en-us/azure/migrate/concepts-migration-webapps#limitations) and therefore it can't be used to migrate web apps directly from physical servers. However, we can use it at least to perform the assessment of our web apps and use the [App Service migration assistant tool](https://learn.microsoft.com/en-us/azure/app-service/app-service-asp-net-migration) for the migration.**
+
 
 Open the [Azure Portal](https://portal.azure.com) and navigate to the previousley created Azure Migrate project. Select *Servers, databases and web apps*, make sure that the right Azure Migrate Project is selected and click on *Assess* and select *Azure App Service (Preview)* from the drop down list.
 
@@ -49,7 +51,8 @@ Review the output of the assessment to see if the web app currently running on W
 
 ### **Task 2: Modernize web app to Azure App Service Code**
 
-**💥 As mentioned ubove, the current [limitations](https://learn.microsoft.com/en-us/azure/migrate/concepts-migration-webapps#limitations) will not allow the direct migration of web apps running on physical machines. Therefore, we will use the [App Service migration assistant tool](https://learn.microsoft.com/en-us/azure/app-service/app-service-asp-net-migration) for the migration.**
+> [!WARNING]
+> **As mentioned ubove, the current [limitations](https://learn.microsoft.com/en-us/azure/migrate/concepts-migration-webapps#limitations) will not allow the direct migration of web apps running on physical machines. Therefore, we will use the [App Service migration assistant tool](https://learn.microsoft.com/en-us/azure/app-service/app-service-asp-net-migration) for the migration.**
 
 
 Login to the Virtual Machine *frontend1* in the *source-rg* Resource Group via Azure Bastion, open the [Azure Portal](https://portal.azure.com) from the *frontend1* VM and navigate to the previousley created Azure Migrate project. Select *Servers, databases and web apps*, make sure that the right Azure Migrate Project is selected and click on *Replicate* within the *Migration tools* box.
@@ -94,7 +97,10 @@ Make sure to remove any blanks for the AzureSiteName parameter as this is not su
 
 Execute the *Invoke-SiteMigration.ps1 -MigrationSettingsFilePath .\\MigrationSettings.json* script.
 
-**💥 If you receive a 401 Unauthorized error it could be that Basic Authentication is disabled on the App Service due to Azure Policy enforcement in your environment. For the current version (June 2023) of the App Service migration scripts this is a requirement**
+> [!WARNING]
+> **If you receive a 401 Unauthorized error it could be that Basic Authentication is disabled on the App Service due to Azure Policy enforcement in your environment. For the current version (June 2023) of the App Service migration scripts this is a requirement**
+
+
 
 ![image](./img/modernize11.png)