+ Generate a .env snippet to configure Pabawi for Azure VM provisioning and management.
+
Your Azure subscription ID (required)
+Azure Active Directory tenant ID
+Service Principal application (client) ID
+Service Principal client secret value
+Comma-separated list of resource groups to scope inventory (leave empty for all)
+
+ Copy the generated snippet below and paste it into your backend/.env file, then restart the application.
+
{maskedSnippet}
+
+ Next: Paste into backend/.env and restart the application. Then check the Integration Status dashboard to verify the connection.
+
+ Fill in the Subscription ID above to generate a complete snippet. +
++ Create a dedicated Service Principal with least-privilege permissions for Pabawi: +
++ Tip: For production, use a custom role with only the specific VM actions Pabawi needs, rather than the full Virtual Machine Contributor role. +
+Test your credentials using the Azure CLI before configuring Pabawi:
+ +{cliTest}
+ After pasting the snippet into backend/.env, restart the backend:
Create and configure Azure VMs
+Start, stop, restart, and deallocate
+View VMs across resource groups
+Error: "Azure authentication failed" or "AuthenticationFailed"
+Error: "AuthorizationFailed" or "The client does not have authorization"
+Error: "Connection timeout" or "ECONNREFUSED"
++ For detailed documentation, see the Azure Integration guide in the documentation. +
+