Introduction
ARVO Studio uses AI from your own account as the final end user of ARVO Studio. The connection is to your Azure AI Foundry deployment or your Anthropic account, running under your own agreement with that provider and billed to you. This is a control feature rather than a restriction and it keeps the choice of provider, the commercial relationship and the off switch with the customer.
Note: AI runs on the customer’s own Azure AI Foundry deployment or Anthropic account and is paid for by the customer. Bluefort does not resell, supply or absorb AI capacity, and AI usage is not included in the ARVO fee.
What you control
You choose which provider to connect, using either the Azure AI Foundry deployment in your own Azure subscription or your own Anthropic account, with one connection active at a time. The keys stay in your setup, they are write only once saved and you rotate them on your own schedule. Because the account is yours, your existing agreement with that provider governs the AI usage, and the provider bills you directly for it.
Turning AI off
AI Operations Enabled is the switch for the whole environment. Turn it off and AI operations in that environment stop immediately, and the changed by and changed at fields record who made the change and when. Customers may use this as an everyday governance control as well as an emergency one, for example during a change freeze or outside working sessions. Separately, and beyond anything Bluefort can override, you can revoke the application’s consent in your own tenant.
The providers’ responsibility
Throughput, throttling, quotas, latency and regional availability are set by Microsoft and by the model provider you have chosen, not by Bluefort. If an AI action is slow, throttled or refused because a quota has been reached, the constraint belongs to your provider account and needs to be resolved there. Planning capacity for a busy project is therefore part of preparing your own deployment.