Introduction
Test Connection is the first thing to run when ARVO Studio has been set up but will not start work in an environment. This article explains what that check covers, where the message list is maintained, and how to decide which part of the configuration to look at first.
This section assumes the environment has already been licensed and activated. If it has not, start with Activate an environment and return here once the access key indicator is on.
Test Connection checks
Test Connection confirms three separate things:
- that the entitlement can be reached and is valid
- that the selected AI connection is successful and responding
- that the required identities can authenticate
Reading the result in those three parts is the quickest way to narrow down a setup problem, because each part points at a different group of fields on ARVO Studio Setup.
Where the messages are maintained
Each Test Connection message, what it means and the first action to take are held in a single table in Kill switches and Test Connection pages. Read the message there first, then use the guidance below to work through the area it points at.
If the entitlement check fails
Start with the Bluefort Connection group on ARVO Studio Setup and look at the Access key configured indicator. On means the key is stored and entitlement verification is active. If a licensed environment still shows it as off, enter the access key again and save; the key is write-only, so it is never displayed back to you and re-entering it is the normal remedy. If the indicator still does not turn on, ask your Bluefort contact to confirm which Business Central environment and Microsoft Entra tenant the entitlement was provisioned against, because activation binds one entitlement to one environment and one tenant.
If the AI connection check fails
AI runs on the customer’s own Azure AI Foundry deployment or Anthropic account, so this part of the check is about the connection details held in Setup. Confirm that only one AI connection is enabled, because Foundry and Anthropic direct are not meant to be active at the same time. Check the endpoint or API address and the deployment or model value against what exists on the customer’s own side, and remember that keys are write-only: if the key has been rotated at the provider, the new one has to be entered in Setup again before the connection will respond. Finally, check that AI Operations Enabled is on, since that switch stops AI operations for the whole environment immediately when it is turned off.
If the identities cannot authenticate
Two identities are involved. The Test Identity is used when generated tests run in the sandbox, and the Orchestrator is used by ARVO Studio for build and deployment operations. Both are entered with the same kind of details: user, security identifier, client identifier, tenant identifier, client secret and a stored-secret indicator. Check the entered values against what was created in Microsoft Entra and confirm that the required Business Central permissions have been assigned. Secrets are write-only here as well, so a secret rotated on the customer’s own schedule must be re-entered before authentication will succeed.