sme updates

Author: katarzyna-koltun-mx

content/en/docs/deployment/mx-azure/_index.md

@@ -3,45 +3,70 @@ title: "Mendix on Azure"
 url: /developerportal/deploy/mendix-on-azure/
 description: "Presents documentation on deploying your Mendix app on Microsoft Azure."
 weight: 42
+no_list: false 
+description_list: true
 ---
 
-{{% alert color="info" %}} This feature is currently available to participating customers. For more information, contact your Customer Service Manager. {{% /alert %}}
+{{% alert color="info" %}} This feature is currently available to participating customers. For more information, contact your Customer Success Manager. {{% /alert %}}
 
 ## Introduction
 
 Mendix on Azure provides a simplified, integrated way to deploy Mendix applications to a Microsoft Azure environment. With this solution, users are empowered to deploy their Mendix applications in Azure environments without the need for intricate infrastructure setup in cloud services. They can also seamlessly manage infrastructure services through an intuitive user interface. No matter their IT skills, users can realize their project value quickly and securely with Azure.
 
-## Features of Mendix on Azure
+## Benefits of Mendix on Azure
 
-Mendix on Azure has the following features:
+By eliminating manual setup and maintenance, Mendix on Azure allows your teams to:
 
-* You can create the managed app in Azure and link it to your Mendix Private Cloud environment.
-* You do not need to perform software upgrades, as they are done for you.
-* The environment is set up in an opinionated way according to the architecture prepared by Mendix.
+* Focus on developing business value instead of configuring infrastructure.
+* Avoid delays caused by cross-team dependencies or architectural discussions.
+* Accelerate time-to-market for critical applications.
+* Address deployment and operational bottlenecks by automating the setup and management of Mendix applications on Azure. 
+* Eliminate the need for specialized cloud engineers and reduce setup time to under 30 minutes. 
+* Focus on innovation and deliver value faster, reduces labor costs, and ensure consistency, security, and compliance.
 
-## Typical Use Cases
-
-Mendix on Azure supports the following use cases:
+## Mendix on Azure and Mendix for Private Cloud
 
-* Geographical data control - For organizations which must keep data within certain regions due to legal or contractual obligations.
-* Industry-specific compliance - For industries such as healthcare, finance, or government, which have strict regulatory compliance requirements.
-* App data sensitivity - For applications which deal with highly sensitive data or are subject to stringent security regulations, Mendix on Azure provides the option to keep this data within the organization's own security perimeter.
-* Legacy systems integration - For integrating with existing legacy systems that are not easily migrated to a public cloud.
+Mendix on Azure is a new deployment option that makes use of some of the features of Mendix for Private Cloud, but does so in an opinionated way. 
 
-## Mendix on Azure and Mendix for Private Cloud
+Mendix for Private Cloud offers its users flexibility coupled with the ability to keep their deployment within their enterprise firewall, but requires more effort to configure and more time to value than deployments on Mendix Cloud. 
 
-Mendix on Azure is a new deployment option that makes use of some of the features of Mendix for Private Cloud, but does so in an opinionated way. Mendix for Private Cloud offers its users flexibility coupled with the ability to keep their deployment within their enterprise firewall, but requires more effort to configure and more time to value than deployments on Mendix Cloud. Mendix on Azure builds on that by providing an automated, preconfigured solution with access to private customer networks, which can be deployed in 30 minutes by a user without IT skills at no extra operational costs. The architecture, its maintenance, updates, and security hardening are all fully managed by Mendix.
+Mendix on Azure builds on that by providing an automated, preconfigured solution with access to private customer networks, which can be deployed in 30 minutes by a user without IT skills at no extra operational costs. The architecture, its maintenance, updates, and security hardening are all fully managed by Mendix. This helps prevent issues with setting up the infrastructure, which can sometimes be very technical and complicated for citizen developers.
 
 ## Architecture
 
+Mendix on Azure provides a managed service to host Mendix apps in an Azure subscription you own. The Mendix on Azure service is composed of several underlying Azure services combined with the following Mendix-specific components:
+
+* [Mendix Runtime](/refguide/runtime/)
+* [Mendix Operator](/developerportal/deploy/private-cloud-cluster/)
+* [Mendix Agent](/developerportal/deploy/private-cloud-cluster/)
+
+Mendix operates all services and components within the scope of the Mendix on Azure service for you. The service leverages several underlying Azure services that are preconfigured to optimally host your Mendix apps.
+
+### Components
+
+Mendix deploys, operates and is responsible for overall service functionality of the following components as part of Mendix on Azure:
+
+* Azure Kubernetes Service with Managed NGINX Ingress Controller (app routing add-on)
+* Azure PostgreSQL Flexible Server
+* Azure Container Registry
+* Azure Blob Storage
+* Azure Managed Grafana
+* Azure Managed Prometheus
+* Azure Virtual Network with private endpoints and private DNS zones
+* Mendix Runtime
+* Mendix Operator
+* Mendix Agent
+
+You cannot alter these managed components yourself beyond what is offered in the Mendix on Azure and Mendix Private Cloud self-service portals. Mendix limits customization to ensure a consistent, predictable, and scalable customer experience.
+
+### Diagram
+
 The diagram in this section presents the high-level architecture of the Mendix for Azure solution.
 
 {{< figure src="/attachments/deployment/mx-azure/architecture.png" class="no-border" >}}
 
 The architecture is assessed against the [Azure well-architected framework](https://learn.microsoft.com/en-us/azure/well-architected/) to ensure its reliability, accessibility, and performance.
 
-The Mendix on Azure solution uses PostgreSQL as the database. PostgreSQL is a cost-effective solution that can provide Mendix on Azure with all required functionalities. It is also the most common and thoroughly tested database option for Mendix in general.
-
 ## Security
 
 Mendix accesses customer environments in a secure, auditable way:

content/en/docs/deployment/mx-azure/mx-azure-getting-started.md

@@ -5,7 +5,7 @@ description: "Documents the pre-implementation tasks for Mendix on Azure."
 weight: 10
 ---
 
-{{% alert color="info" %}} This feature is currently available to participating customers. For more information, contact your Customer Service Manager. {{% /alert %}}
+{{% alert color="info" %}} This feature is currently available to participating customers. For more information, contact your Customer Success Manager. {{% /alert %}}
 
 ## Introduction
 
@@ -16,6 +16,7 @@ Before you can deploy your Mendix app on Azure, you must plan and complete a num
 To adopt Mendix on Azure, you need to have the following:
 
 * A Mendix account; Mendix Studio Pro 10.10 or newer is required
+* As an optional best practice, add multiple cluster manager to your clusters
 * An Azure account with the following permissions:
     * Permission to grant admin consent on the Mendix on Azure portal app registration
     * Owner or Contributor role assigned on the target subscription level
@@ -56,46 +57,4 @@ To adopt Mendix on Azure, you need to have the following:
 
 Mendix on Azure is available for purchase from the the [Azure Marketplace](https://azuremarketplace.microsoft.com/). Connecting to Azure services may also include additional cost. For more information, refer to Azure documentation.
 
-For production environments, you also need a license for your Mendix app. For more information, refer to [Licensing Apps](/developerportal/deploy/licensing-apps-outside-mxcloud/).
-
-## Shared Responsibility Model
-
-Under the shared responsibility model for Mendix on Azure deployments, Mendix, Microsoft, and customer organizations all have their own responsibilities in the deployment process and business-as-usual operations. Familiarize yourself with the responsibilities listed below:
-
-### Microsoft Responsibilities
-
-Microsoft is responsible for operating and securing the Azure services underlying the Mendix on Azure service. This includes the following services:
-
-* Compute
-    * Azure Kubernetes service
-* Storage
-    * Azure Blob Storage
-    * Azure Container Registry
-* Database
-    * PostgreSQL Flexible Server
-* Networking
-    * Virtual networks
-    * Load balancer
-    * Private endpoints
-* Monitoring
-    * Managed Grafana and Prometheus
-
-### Mendix Responsibilities
-
-Mendix is responsible for orchestrating, operating, maintaining, securing, and supporting the Mendix on Azure service. This includes the following tasks:
-
-* Orchestrating - Ensure that the underlying Azure services function together as one cohesive offering.
-* Operating - Resolve regressions in how the underlying Azure services come together as one service.
-* Maintaining - Ensure that the service absorbs changes in the underlying Azure services without impact on customers.
-* Securing - Ensure that the service remains compliant with relevant security best practices and frameworks.
-* Supporting - Reactively address customer issues with using the service.
-
-### Customer Responsibilities
-
-Customers are responsible for developing, deploying, operating, integrating, and securing apps on top of the Mendix on Azure service. This includes the following tasks:
-
-* Developing - Create apps that deliver business outcomes.
-* Deploying - Deploy apps.
-* Operating - Monitor app behavior and address deviations.
-* Integrating - Securely integrate apps with backend services and IAM.
-* Securing - Comply with Mendix best practices for secure apps.
+For production environments, you also need a license for your Mendix app. For more information, refer to [Licensing Apps](/developerportal/deploy/licensing-apps-outside-mxcloud/).

content/en/docs/deployment/mx-azure/mx-azure-installation.md

@@ -5,7 +5,7 @@ description: "Documents the initial configuration tasks for Mendix on Azure."
 weight: 20
 ---
 
-{{% alert color="info" %}} This feature is currently available to participating customers. For more information, contact your Customer Service Manager. {{% /alert %}}
+{{% alert color="info" %}} This feature is currently available to participating customers. For more information, contact your Customer Success Manager. {{% /alert %}}
 
 ## Introduction
 
@@ -19,6 +19,7 @@ Before starting the installation and implementation process, make sure that you
 * Purchase the Mendix on Azure offering in the [Azure Marketplace](https://azuremarketplace.microsoft.com/).
 * Familiarize yourself with the [Private Cloud](https://docs.mendix.com/developerportal/deploy/private-cloud/) concepts.
 * Ensure that your Mendix Studio Pro is in version 10.10 or newer.
+* As an optional best practice, add multiple cluster manager to your clusters.
 
 ## Creating an Azure Cluster
 
@@ -27,7 +28,7 @@ To create a cluster for your Mendix on Azure app, perform the following steps:
 1. In the Mendix Portal, in Private Cloud Cluster Manager, click **Mendix on Azure**.
 2. Connect to your Azure account by clicking **Connect and Initialize**, and then logging in with the same account that you used to purchase the Mendix on Azure offering.
 
-    After you successfully connect the accounts, the Mendix Portal shows a list of available clusters (that is, any Azure clusters that you have already linked with Mendix) and initializable clusters (that is, any clusters that you have not yet linked with Mendix).
+    After you successfully connect the accounts, the Mendix Portal shows a list of available clusters (that is, any Azure clusters that you have already linked with Mendix) and initializable clusters (that is, any clusters that you have not yet linked with Mendix). For initialized clusters, means that the all the required resources are provisioned on the cluster. For uninitialized clusters, no resources are provisioned yet.
 
     {{< figure src="/attachments/deployment/mx-azure/available-clusters.png" class="no-border" >}}
 
@@ -59,8 +60,20 @@ To create a cluster for your Mendix on Azure app, perform the following steps:
 
 10. Click **Initialize**.
 
-    The initialization process takes ca. 15 minutes. It creates a resource group in the managed app. It also automatically adds a namespace and cluster in Private Cloud portal, which you can use to create environments. The cluster cannot be deleted from the Private Cloud portal. If you want to remove it, you must delete it in the Microsoft Azure portal.
+    The initialization process takes ca. 15 minutes. It creates a resource group in the managed app that you created in step 3 above. Once the cluster is initialized successfully, a corresponding cluster and namespace are created in the the Private Cloud portal. The namespace is also configured automatically, as described in [Standard Operator: Running the Tool](https://docs.mendix.com/developerportal/deploy/standard-operator/#running-the-tool). The cluster cannot be deleted from the Private Cloud portal. If you want to remove it, you must delete it in the Microsoft Azure portal.
 
 ## Deploying an App to an Azure Cluster
 
-After creating your cluster in Microsoft Azure, you can deploy now deploy your applications to the cluster. The deployment process is the same as with Mendix for Private Cloud. For more information, see [Deploying a Mendix App to a Private Cloud Cluster](/developerportal/deploy/private-cloud-deploy/).
+After creating your cluster in Microsoft Azure, you can deploy now deploy your applications to the cluster. The deployment process is the same as with Mendix for Private Cloud. For more information, see [Deploying a Mendix App to a Private Cloud Cluster](/developerportal/deploy/private-cloud-deploy/).
+
+## Editing the Cluster in the Mendix on Azure Portal
+
+If required, you can change the following options for your cluster:
+
+* AKS service tier
+* AKS node size
+* VM type
+* Load balancer type
+* Postgres compute SKU
+*  Postgres performance tier for storage IOPS
+* Custom tags