Skip to Content
Setup & ConfigurationAP Automation Client SetupPortal Deployment & Testing

Portal Deployment & Testing

In this section, we will deploy and test our portal. We will be using the App Services and Azure CLI.

From your browser, go to https://portal.azure.com/ .

Create The App Service

  1. Go to App Services > Create

  2. Configure the following:

  • Subscription: Client’s subscription
  • Resource Group: Use the existing one or create new
  • Name: e.g., ap-automation-portal
  • Runtime Stack: Node.js
  • Region: Match with Dataverse for low latency

  1. Select or create an App service plan (Basic or Standard tier is fine for MVP use case)

  2. Setup Service Principal. In Dynamics 365, particularly in the context of integrations and security, a Service Principal is essentially an identity used by an application, service, or automated tool to access resources in your Microsoft Entra ID.

To create a Service Principal, run the following commands in Azure CLI:

  • az login
  • az ad sp create-for-rbac --name "ap-automation-deploy" --role contributor --scopes /subscriptions/<subscription-id>/resourceGroups/<resource-group-name>
  1. Save the following (from previously generated):
  • clientId
  • ClientSecret
  • TenantId
  • subscriptionId
  1. Set the environment variables and deploy

Test if all the data from Dataverse and Business Central is available in the portal.

Last updated on
Business Central IntegrationClient Credentials To Collect