Test the model and service connections
Choose the model service or external provider, then connect the interface and any vector or tracing services. Verify where prompts and responses travel before using sensitive information.
Start with a documented service combination and review every connection before use.
Decide whether the model runs in your infrastructure or through a provider. Choose the interface and any vector or tracing service, then configure the documented connection variables. Test with non-sensitive data first and confirm which systems receive prompts and responses.
Choose the model service or external provider, then connect the interface and any vector or tracing services. Verify where prompts and responses travel before using sensitive information.
Put the service in the appropriate environment and use explicit private connections where supported. Keep server credentials out of browser code and source control.
Use managed roles and the narrowest useful scope. Set expiry for temporary access, inspect effective permissions and revoke the grant when the work is finished.
Detailed instructions are maintained in the product documentation.
No. External providers can still receive requests. Your configuration determines where data goes and which services can access it.
Name an owner and review the service-specific persistence and recovery instructions before relying on its data.
Secret use and secret reveal are separate permissions. Grant sensitive access only when the task requires it.
Bring your code or choose a service, then give the result a clear operating home.
Start building ↗