Introduction
This article covers the controls at the end of the Setup card: the switch that governs whether AI operations can run in the environment at all, the Test Connection check that confirms the rest of the configuration holds together, and the smoke test that proves the testing setup of the environment works.
These are small actions with a good deal of weight behind them, so it is worth knowing exactly what each one does before you need it.
AI Operations Enabled
AI Operations Enabled is the switch for the whole environment. Turn it off and AI operations in that environment stop immediately. Nothing is uninstalled and nothing is deleted, however the environment stops carrying out AI work until the switch is turned back on.
The changed by and changed at fields record who made the change and when, so the action is available for auditing. Treat the switch as a normal governance control rather than only an emergency button. A customer may reasonably disable AI outside working sessions, or for the duration of a change freeze, and turn it back on when work resumes.
The control Bluefort cannot override
The customer also holds a control that sits outside ARVO Studio entirely. A customer can revoke the application’s consent in their own Microsoft Entra tenant, and Bluefort cannot override that decision. It is worth stating this point in the article, because it is usually the first question an IT director would ask about any application that reaches into the environment.
Test Connection
Test Connection checks three things: that the entitlement can be reached and is valid, that the selected AI connection responds, and that the required identities can authenticate. It is the wider of the two connection checks. Test Bluefort Connection, in the Bluefort Connection group, proves only the entitlement and the access key, so use that one when the question is about the licence and Test Connection when the question is about the environment as a whole.
Run it after any change to the access key, to the AI connection, or to either identities.
Messages and what to do first
The table below is maintained in this article only. The Help section links to it rather than keeping a second copy that can drift out of date.
| Message | What it means | First action to take |
| N/A | N/A | N/A |
Run Smoke Test
Test Connection proves that ARVO Studio can reach what it depends on. Run Smoke Test goes one step further and proves that the testing setup of the environment actually works. Open the Testing menu, choose Test Runs, and choose Run Smoke Test.
This process takes roughly 30 to 60 seconds and much of that is deliberate waiting, because ARVO confirms that permission changes have genuinely taken effect before it goes any further.
A pass reports two tests passed and none failed, and the new row in Test Runs shows the status Passed. The testing setup of the environment is then confirmed.
If something is misconfigured the run does not fail silently. It lands with the status Parked, and the reason is named on the run card, typically an expired secret, a missing permission or a wrong tenant id. Correct the item named on the card, then run the smoke test again.
Quick check
Setup is finished when AI Operations Enabled is on, Test Connection completes without reporting an action for you to take, and the smoke test comes back Passed. If a message points at the entitlement, start with Bluefort Connection. If it points at the AI connection, start with Your Azure AI (BYO) or Your Anthropic API (BYO). If it points at an identity, start with Test Identity and Orchestrator.
Updated on 7 September 2026