Get started with a Single Tenant

To start discussing a single tenant, the following questions around compliance, tenant properties and capacity planning have to be answered.

Compliance

Certain compliance and regulatory topics must also be clarified up front as they again have impact on pricing and timeline and must be noted in the contract:

Question

Details

1

In which Azure region should the deployment reside?

https://azure.microsoft.com/en-us/explore/global-infrastructure/geographies/#overview

2

Which Azure regions could be used for any OpenAI or LLM interactions

More regions = more flexibility and potentially better quality.

Check regions for OpenAI Models here: https://learn.microsoft.com/en-us/azure/ai-services/openai/concepts/models

3

Where can the Unique employees maintain the solution be from?

From which locations is Unique allowed to access the single tenant. E.g.: Only CH, CH or EU, only EU

Tenant properties

Before Unique can setup the Azure Single-Tenant for the client the following questions need to be answered by the client:

	Question	Details
1	Which `x.unique.app` URL do they choose?	The customer can select their URL themselves. The self-selected URL must at least be 4 characters long and should not exceed a human readable length otherwise no one can type that. The format is always `https://<selection>.unique.app`. The name must not be generic like `my.unique.app` or `genai.unique.app` but a bit dedicated like `customer-alias-prod.unique.app` or so. The engineering team reserves the right to reject an URL if it was chosen without their consent. If the Client selects their own URL they must consent in written form that this URL will appear in Uniques code base as part of the Infrastructure/Configuration as Code.
2	What shall the tab name be?
3	How should the customers theme look like?	Theming parameters (colours, logo and font) shall be provided by the client. If a customer has a themed organisation on `next.unique.app` the theme can be copied from there. See details here: Theming
4	Is IP-Blocklisting required by the client?	If a customer chooses to leverage IP-Blocklisting they IP-Address ranges need to be provided. Unique offers a dedicated VPN for Unique employees that the Client should allow-list as well as the customer is to warn that Unique will be restricted in supporting them when the block is in place. If the Unique VPN IP is not allowed, the only support option that can be guaranteed is via screen-sharing. IP block costs approx. 600$ per month and is difficult to manage for both sides. It is thus discouraged. Do not propose it to the customer if they do not demand it from their side. If they want it, a premium must be considered.
5	Which IDP is the client using? Does the client want to enable SSO?

Capacity planning

Before Unique can setup the Azure Single-Tenant for the client the following questions need to be answered by the client:

	How many tokens per minute do you expect at the maximum peak?	This is relevant to know if it makes sense to add our model scaler with multiple regions and/or subscription to avoid hitting capacities (e.g. rate limits).
1	How many users will interact with the system at maximums peak and on average?

Author	Dominik Meyer