wrong provider block

Author: viniciusdc

docs/docs/explanations/advanced-provider-configuration.md

@@ -98,35 +98,6 @@ amazon_web_services:
   permissions_boundary: arn:aws:iam::01234567890:policy/<permissions-boundary-policy-name>
 ```
 
-</TabItem>
-
-<TabItem value="azure" label="Azure">
-
-[Microsoft Azure](https://azure.microsoft.com/) has similar settings for Kubernetes version, region, and instance names - using Azure's available values of course.
-
-Azure also requires a field named `storage_account_postfix` which will have been generated by `nebari init`. This allows nebari to create a Storage Account bucket that should be globally unique.
-
-```yaml
-### Provider configuration ###
-azure:
-  region: Central US
-  kubernetes_version: 1.19.11
-  node_groups:
-    general:
-      instance: Standard_D4_v3
-      min_nodes: 1
-      max_nodes: 1
-    user:
-      instance: Standard_D2_v2
-      min_nodes: 0
-      max_nodes: 5
-    worker:
-      instance: Standard_D2_v2
-      min_nodes: 0
-      max_nodes: 5
-  storage_account_postfix: t65ft6q5
-```
-
 ### Launch Templates (Optional)
 
 Nebari supports configuring launch templates for your node groups, enabling you to customize settings like the AMI ID and pre-bootstrap commands. This is particularly useful if you need to use a custom AMI or perform specific actions before the node joins the cluster.
@@ -162,14 +133,43 @@ cluster region by inspecting its respective SSM parameter. For more information,
 [Retrieve recommended Amazon Linux AMI IDs](https://docs.aws.amazon.com/eks/latest/userguide/retrieve-ami-id.html).
 :::
 
-:::warning **Important:** If you add a `launch_template` to an existing node group that was previously created without one, AWS will treat this as a change requiring the replacement of the entire node group. This action will trigger a reallocation of resources, effectively destroying the current node group and recreating it. This behavior is due to how AWS handles self-managed node groups versus those using launch templates with custom settings.
+:::warning If you add a `launch_template` to an existing node group that was previously created without one, AWS will treat this as a change requiring the replacement of the entire node group. This action will trigger a reallocation of resources, effectively destroying the current node group and recreating it. This behavior is due to how AWS handles self-managed node groups versus those using launch templates with custom settings.
 :::
 
-:::hint **Recommendation:** To avoid unexpected downtime or data loss, consider creating a new node group with the launch template settings and migrating your workloads accordingly. This approach allows you to implement the new configuration without disrupting your existing resources.
+:::tip To avoid unexpected downtime or data loss, consider creating a new node group with the launch template settings and migrating your workloads accordingly. This approach allows you to implement the new configuration without disrupting your existing resources.
 :::
 
 </TabItem>
 
+<TabItem value="azure" label="Azure">
+
+[Microsoft Azure](https://azure.microsoft.com/) has similar settings for Kubernetes version, region, and instance names - using Azure's available values of course.
+
+Azure also requires a field named `storage_account_postfix` which will have been generated by `nebari init`. This allows nebari to create a Storage Account bucket that should be globally unique.
+
+```yaml
+### Provider configuration ###
+azure:
+  region: Central US
+  kubernetes_version: 1.19.11
+  node_groups:
+    general:
+      instance: Standard_D4_v3
+      min_nodes: 1
+      max_nodes: 1
+    user:
+      instance: Standard_D2_v2
+      min_nodes: 0
+      max_nodes: 5
+    worker:
+      instance: Standard_D2_v2
+      min_nodes: 0
+      max_nodes: 5
+  storage_account_postfix: t65ft6q5
+```
+
+</TabItem>
+
 <TabItem value="do" label="DigitalOcean">
 
 DigitalOcean has a restriction with autoscaling in that the minimum nodes allowed (`min_nodes` = 1) is one but is by far the least expensive provider even accounting for `spot/pre-emptible` instances.