Create or Update the Business Central Client Secret (Azure + Paystand Dashboard)

Article type: How-to

Audience: Paystand Dashboard admins and Microsoft Entra ID (Azure) administrators who maintain the Business Central connection

Last reviewed: August 17, 2026

__________________________________________________

Summary

Need Client Value only to save Dashboard settings? Do not create a new secret yet. Start with How to Find Your Current Business Central Client Value (Without Rotating the Secret). Use this article only when the current Value cannot be recovered, the secret is expired, or you are intentionally rotating.

Paystand authenticates to Business Central with a Microsoft Entra ID app registration client secret. To create or rotate that secret, generate a new client secret in Azure, copy the Value (not the Secret ID), and paste it into the Paystand Dashboard field labeled Client Value. You also need Client Value whenever you change other Business Central connection settings, such as GL account mappings.

__________________________________________________

Who this is for (roles)

Microsoft Entra ID (Azure)

  • Role: Application Administrator or Global Administrator
  • Needed for: Creating and rotating client secrets under Certificates & secrets

Paystand Dashboard

  • Role: Admin (can open Integrations and save the Business Central connection)
  • Needed for: Pasting Client Value / Client ID and reconnecting
  • Note: Clerk / AR users typically do not manage integration credentials

If you cannot see Integrations or cannot save, ask a Paystand Dashboard Admin on your account to complete Part 2.

__________________________________________________

Important terminology

  • In Azure, copy the Value column — that is the client secret.
  • Do not copy the Secret ID — Paystand does not use it for authentication.
  • In the Paystand Dashboard, paste that Value into Client Value.

__________________________________________________

Before you begin

  • An existing Paystand app registration (usually named Paystand), created during Business Central setup
  • The Azure Application (client) ID from that app registration Overview page
  • A secure place to store the new secret Value (for example, your company password manager)

If you are connecting Business Central for the first time, complete the Business Central Implementation Guide first. This article covers only secret creation/rotation and updating Client Value in Paystand.

__________________________________________________

Part 1 — Create or rotate the client secret in Microsoft Entra ID

Step 1: Open the Paystand app registration

  1. Sign in to the Azure portal or Microsoft Entra admin center.
  2. In the top search bar, type App registrations and open it.
  3. Open the Paystand application registration. If you manage multiple tenants, confirm you are in the correct Microsoft Entra tenant.
  4. Under Manage, select Certificates & secrets.
  5. Select the Client secrets tab.

Azure Certificates and secrets page with Client secrets tab

__________________________________________________

Step 2: Create a new client secret

  1. Click + New client secret.
  2. In Description, enter a recognizable name (for example, Paystand secret).
  3. In Expires, choose 730 days (24 months) or your organization’s preferred rotation period. Microsoft also offers 180 days, 365 days, or a custom date.
  4. Click Add.

Paystand’s Business Central integration uses a client secret in the Dashboard Client Value field (not a certificate).

Azure Add a client secret pane

__________________________________________________

Step 3: Copy the secret Value immediately

  1. Locate the row you just created in the Client secrets table.
  2. In the Value column, click Copy to clipboard.
  3. Store the Value in a secure location.

Critical: Azure shows the full secret Value only once. If you leave the page without copying it, you cannot retrieve it later — you must create another secret.

Do not copy the Secret ID.

Azure client secrets table highlighting the Value column

__________________________________________________

Step 4: Plan for expiration

  1. Before the secret expires, create a new client secret (repeat Part 1).
  2. Update Client Value in the Paystand Dashboard (Part 2).
  3. After you confirm the connection works, delete the old expired secret in Azure.

If a secret expires without rotation, the Business Central connection stops working until a new Value is saved in Paystand.

__________________________________________________

Part 2 — Enter the secret in the Paystand Dashboard

Step 1: Open the Business Central integration

  1. Sign in to the merchant Paystand Dashboard as an Admin.
  2. In the left navigation, go to Integrations.
  3. If a submenu appears, select Integrations again.
  4. Scroll to Microsoft Dynamics 365 Business Central.
Paystand Dashboard Integrations page showing Business Central

__________________________________________________

Step 2: Expand the connection form

  1. Confirm the integration status (Connected or Inactive).
  2. Click Connect To Business Central to expand the form.

The form includes Environment, Company Name, Tenant Name, bank account IDs, GL accounts, Client ID, and Client Value.

Expanded Business Central connection form

__________________________________________________

Step 3: Paste Client Value and save

  1. Confirm Client ID matches the Azure Application (client) ID.
  2. In Client Value, paste the Azure secret Value from Part 1.
  3. Leave other fields unchanged unless you also intend to update them (for GL or bank changes, see the related article below).
  4. Click Connect To Business Central.
  5. Wait for Connected to Business Central, and confirm status is Connected.

Security note: Paystand does not redisplay a previously saved Client Value. The field looks blank when you reopen the form — that is expected. Paste the secret whenever you need to save.

Client ID and Client Value fields on the Business Central form

__________________________________________________

Verify

  1. Dashboard status for Business Central shows Connected.
  2. You see the confirmation message Connected to Business Central after saving.
  3. Optional: confirm a recent payment or receivable sync still completes normally after the change.

__________________________________________________

Troubleshooting

Symptom: Save / Connect button stays disabled
Likely cause: Required field empty — usually blank Client Value
What to do: Paste Client Value; confirm all required connection fields are filled

Symptom: Authentication error or “Invalid client secret provided”
Likely cause: Wrong value, truncated value, Secret ID pasted, or expired secret
What to do: Create a new secret in Azure, copy the full Value, paste into Client Value, reconnect

Symptom: Connection worked before but stopped
Likely cause: Secret expired
What to do: Check Expires in Azure Certificates & secrets, create a new secret, update Paystand

Symptom: Client Value is blank when reopening the form
Likely cause: Expected security behavior
What to do: Paste the current or new secret again when saving

Symptom: Cannot find App registrations in Azure
Likely cause: Insufficient Azure role
What to do: Ask an Application Administrator or Global Administrator to perform Part 1

Symptom: Cannot see Integrations or cannot save in Paystand
Likely cause: Insufficient Paystand Dashboard role
What to do: Ask a Dashboard Admin to complete Part 2

__________________________________________________

Still not resolved?

Contact Paystand Support and include:

  • Merchant / company name and environment (Production or Sandbox)
  • Whether you created a new Azure secret and updated Client Value
  • Exact error text from the Dashboard (if any)
  • Screenshot of Azure Certificates & secrets showing the secret Exists/Expires row (do not include the secret Value)

__________________________________________________

Related articles

References (Microsoft)

Was this article helpful?
0 out of 0 found this helpful