Skip to content

Commit 06d9cab

Browse files
Merge pull request mendix#9219 from MXClyde/development
Documentation fixes
2 parents fd9ddb8 + a14a827 commit 06d9cab

2 files changed

Lines changed: 2 additions & 2 deletions

File tree

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ To adopt Mendix on Azure, you need to have the following:
1919
* As an optional best practice, add multiple cluster manager to your clusters
2020
* An Azure account with the following permissions:
2121
* Permission to grant admin consent on the Mendix on Azure portal app registration
22-
* Owner or Contributor role assigned on the target subscription level
22+
* Owner role assigned on the target subscription
2323

2424
{{% alert color="info" %}} To comply with the principle of least privilege, you can also create a custom role for the Mendix Operator instead of assigning the Owner or Contributor role. For the required permissions, see below:
2525

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ Before starting the installation and implementation process, make sure that you
1717

1818
* Obtain and configure a Microsoft Azure account. For more information, refer to the the Microsoft Azure documentation.
1919
* Purchase the Mendix on Azure offering in the [Azure Marketplace](https://azuremarketplace.microsoft.com/).
20-
* Enable co-access permissions for the offering.
20+
* You must sign in to the Mendix on Azure portal with the same Azure account that was used to purchasing the offering. If you sign in with another account, the cluster is not visible for initialization.
2121

2222
{{< figure src="/attachments/deployment/mx-azure/coadmin-permission.png" class="no-border" >}}
2323

0 commit comments

Comments
 (0)