Deploy

To deploy this package, all you have to do is click the button below. It will automatically deploy the following resources for you,

• Azure Key Vault
• Azure App Service Plan
• Azure SQL server and database
• Azure App Service

You only need to provide a few parameters to complete the deployment. Before continueing to deploy you need to create an Azure AD App Registration that will be used to authenticate to the site and provide the tokens needed to use IntuneCD.

Create Azure AD App Registration

• Head over to App Registrations in Azure AD and click New registration, provide a name, choose multi tenant and click register

• Add all API permissions as stated in the IntuneCD Documentation and grant admin consent.

• Click on App Roles and create a new role, the Value must be set to "intunecd_admin"

• Continue to create a secret for the application and save the secret value, then go to the Enterprise app and note down the Client ID and Object ID.

⚠️ IMPORTANT NOTE: Get the Object ID from the Enterprise App, not the App Registration.

Deploy to Azure

Click the button below and fill out the fields that are not pre-populated, the name of the App Service will be the same as configured under IntuneCD Instance Name

NOTE: admin or administrator are not valid usernames for the SQL db user.

NOTE: Selecting the B1 IntuneCD Farm Sku might cause issues like not being able to run more than one backup/update at a time.

Once succussfully deployed, go back to the App Registration and add a new Web redirection URI, add the following URIs:

• https://{your_app_service_name}.azurewebsites.net/auth/signin-oidc
• https://{your_app_service_name}.azurewebsites.net/tenants

Navigate to Azure AD Enterprise Applications and click on the IntuneCD Monitor app, add or edit an account you wish to be an admin in IntuneCD Monitor and assign the role created in prevoius steps.

That's it. After a successful deployment you will be able to navigate to https://{your_app_service_name}.azurewebsites.net and see the below window. If you see a 502 Bad Gateway, be patient, the deployment is most likely not finished.