Introduction
The Bluefort Connection group is where the environment’s licence is confirmed. Entering the access key tells ARVO Studio which entitlement this sandbox is running under, and it is the first thing to complete on Setup.
If the environment has not been activated yet, start with Activate an environment. This article covers the fields in the group, how the connection is verified, and how to look after the key.
What this group is for
An environment entitlement binds one Business Central environment and one Microsoft Entra tenant to one end customer. The access key is the credential that connects the sandbox to that entitlement, so that ARVO Studio can verify it at the start and keep verifying it while the environment is in use. Little else in Setup is worth completing until this group is done, because AI actions only become available on a licensed environment.
Fields
Complete the following on ARVO Studio Setup, in the Bluefort Connection group.
| Field | What to enter | Notes |
| Bluefort Access Key | The key issued at activation. Partner Edition: from your Bluefort contact. Direct subscription: issued in-app at purchase. | Write only and masked. After saving, the key is not shown again, and the Access key configured indicator turns on to confirm that a key is stored. |
| Environment Name | The name of this Business Central environment, exactly as it appears in the Business Central admin centre. | Several ARVO functions build service URLs from this value, so it must match the admin centre exactly. If a licensed environment still shows Access key configured as off, check this field as well as the key. |
Test Bluefort Connection
Test Bluefort Connection is the verification action for this group, and it sits on the Setup page. A healthy result confirms two things: the key has been accepted, and the entitlement behind it is active. This should be run whenever the key is entered in the beginning or changed.
Where the check does not succeed it names the reason rather than failing silently, and that reason will be one of three kinds. The key may not be recognised, which usually means it has been mistyped or belongs to another environment. The entitlement may not be active, in which case the licence itself needs attention and your Bluefort contact person can confirm what it is bound to. Or the service may not have been reachable, which points at the network or a temporary outage rather than at anything in Setup.
Quick check
Save the key, confirm that Access key configured turns on, and check that Environment Name matches with the one in the admin centre. Then choose Test Bluefort Connection and confirm a healthy result. Test Connection, described in Kill switches and Test Connection, is the wider check that also covers the AI connection and the identities.
If you no longer have the key
The access key is write only, so it cannot be read back from Setup once it has been saved. This should be stored with the customer’s other environment credentials.
Keys are issued per customer environment rather than per person, so a single key is not shared out among individual consultants. Treat it as you would a password: do not email it around, and do not store it in source control.