TOGETHER On-Premises Environments
π€ Generated with Claude Code
β Reviewed by Martin Riemann, 2026-09-02
Co-Authored-By: Claude (noreply@anthropic.com)
FACHTEST, STAGE and PROD are the three Together server environments. Each is a self-contained copy of the same shape, running on our own hardware, with its own domain controllers β which is why the same host name exists three times over.
This page describes the shape of an environment and the contract every server presents to
the applications on it. The machine inventory itself β addresses, operating systems, which
application sits on which server β belongs in infrastructure/servers/together/ and is not
yet written.
What every environment containsβ
| Role | Name | Typically | What it does |
|---|---|---|---|
| Application | TISAPP* | 3 | IIS applications, Windows services, scheduled tasks |
| Database | TISDB* | 2 | SQL Server |
| Web | TISWEB* | 2 | terminates the public host name, reverse-proxies to the application servers |
| Domain controller | TISDC* | 2 | Active Directory for the environment |
| Utility | TISUTIL | 1 | operations and administration |
Three things about this surprise people:
- Only one web server is active. There is no load balancer in front of the pair, so the second machine is a standby, not capacity. A web-server outage is a full outage until someone switches over.
- Host names repeat across environments.
TISAPP01exists in Fachtest, in Stage and in Prod. A server name therefore never identifies a machine on its own β always say the environment with it. - The counts are typical, not fixed. Fachtest carries a fourth application server
(
TISAPP003) in the Arc onboarding inventory β the machine being replaced byTISAPP03. Hardware is renewed every few years, and names are usually swapped between the0xand00xforms as servers migrate, so the digit count says nothing about a server's role.
Environment variables on every serverβ
Who does this: DevOps team. Reading the values needs access to the server, and changing one is a machine-wide operation with a restart attached β ask rather than edit.
Five machine-level environment variables are set on every server in every Together environment. Between them they answer two questions for every application on the machine: which environment am I? and who am I in Azure?
| Variable | Value | Read by |
|---|---|---|
ASPNETCORE_ENVIRONMENT | Fachtest, Stage or Prod | ASP.NET Core applications under IIS |
DOTNET_ENVIRONMENT | the same value | Windows services and workers (generic host) |
AZURE_TENANT_ID | 13d188a3-27b5-44c8-a858-a4c34d245819 | DefaultAzureCredential |
AZURE_CLIENT_ID | the service principal for this server or environment | DefaultAzureCredential |
AZURE_CLIENT_SECRET | its client secret | DefaultAzureCredential |
Which environment am I?β
Both name variables are set because both .NET host models are in use on the same servers. A
web application built with WebApplication.CreateBuilder reads ASPNETCORE_ENVIRONMENT; a
Windows service or worker built on the generic host reads DOTNET_ENVIRONMENT. Several of
ours are the latter β tis.volltextsuche.gf.import.service,
tis.volltextsuche.omds.import.service, tis.gf.wrka.worker, OmdsxManager and
OmdsCollector. The two variables therefore MUST hold the same value: if they diverge, a
web application and a service on the same machine load different configuration.
What the value decides:
- the
appsettings.<Environment>.jsonoverlay applied on top ofappsettings.json IsTisFachtest(),IsTisStage(),IsTisProduction()andIsTisTestEnvironment()fromTis.Hosting.Extensions, which is how services branch on environment- which Key Vault the application loads, through its own
appsettingsentry
The canonical values come from TisEnvironments in Tis.Hosting.Extensions: Fachtest,
Stage, Prod, plus the standard Development. Comparison is case-insensitive β
FACHTEST, fachtest and Fachtest all match, which is why the repositories carry every
spelling of every environment. New files SHOULD use the canonical form anyway.
Who am I in Azure?β
The three AZURE_* variables are the service principal credentials that
DefaultAzureCredential picks up. This is how an application authenticates against Key Vault
at start-up, and it is the reason no secret has to be deployed alongside the application.
Prod gives each server its own service principal; Fachtest and Stage share one per environment. Client IDs, group assignments and vault permissions are in ../secrets/README.md β this page states only the shape.
Machine-level, and what follows from thatβ
The variables are set at machine level. No per-application-pool overrides are in use, which has two consequences:
- Every application on a server sees the same values. One application cannot run as a different environment, or as a different Azure identity, than its neighbours on the same machine.
- A change reaches only processes started afterwards. Setting the variable is not enough: the application pool has to be recycled, or the Windows service restarted.
To read the current values on a server:
[Environment]::GetEnvironmentVariable("ASPNETCORE_ENVIRONMENT", "Machine")
[Environment]::GetEnvironmentVariable("DOTNET_ENVIRONMENT", "Machine")
[Environment]::GetEnvironmentVariable("AZURE_TENANT_ID", "Machine")
[Environment]::GetEnvironmentVariable("AZURE_CLIENT_ID", "Machine")
AZURE_CLIENT_SECRET is deliberately not in that list. Do not print it and do not paste it
into a ticket β treat a printed secret as one that needs rotating.
When one of them is wrongβ
None of these failures degrades gracefully β which is the good news. Because the values are machine-wide, a wrong one is noisy: it breaks every application on the server at once rather than quietly misrouting a single one.
| Problem | Symptom |
|---|---|
| Wrong environment name | the wrong appsettings overlay is loaded, and applications across the machine start erroring against the wrong systems |
| Environment name unset | .NET falls back to Production, so appsettings.Prod.json is not loaded while IsTisProduction() is nevertheless true |
AZURE_* missing, or an expired secret | Key Vault loading fails and the application fails at start-up β there is no fallback to a local value |
What differs between the threeβ
Entry points and deploymentβ
| Environment | Host | API gateway | Deployment group |
|---|---|---|---|
| Fachtest | fachtest.servicebytogether.at | api-fachtest.togethercca.com | fachtest.servicebytogether.at |
| Stage | stage.servicebytogether.at | api-stage.togethercca.com | stage.servicebytogether.at |
| Prod | www.servicebytogether.at | api.togethercca.com | www.servicebytogether.at |
The Azure DevOps deployment groups carry the same strings as the host names. A release stage picks its machines by deployment group plus tag β see Build and Release Pipelines.
Deployed web applications land under D:\deployed-webapps\ on the target server, served by
IIS under a virtual path matching the application name. Not everything is a web application:
tis.gf.abgleich installs a scheduled task instead, and standalone applications sit under
D:\deployed-apps\.
Identity and monitoringβ
| Environment | Key Vault | Subscription | Service principal | Arc + AMA |
|---|---|---|---|---|
| Fachtest | at-tgca-tis-f-default | Together-Fachtest | shared: fachtest-apps | β |
| Stage | at-tgca-tis-s-default | Together-Fachtest | shared: stage-apps | β |
| Prod | at-tgca-tis-p-default | Together-Prod | one per server: prod-tisapp01-apps, β¦ | β |
Not part of the standard shapeβ
- ADFS and the Web Application Proxy (
TISADFS001,TISWAP001) sit outside the five roles above; the Arc plan defines an ADFS data collection rule for Prod only. - Stage is being retired. The servers still run and are configured like the others β see stage-decommissioning.md for the decision and the cleanup.
Development is not one of themβ
DEVELOPMENT is the developer's own machine, and it is deliberately not built like a server environment:
- No
AZURE_*variables.DefaultAzureCredentialfalls back to the signed-in user, so a service usually runs locally with no secret setup at all. That is read access, and only to the development vault. appsettings.Local.jsonis loaded after Key Vault, and only when the environment isDevelopment. It is the intended place for a value the development vault does not have β along withdotnet user-secrets, and unlikeappsettings.Development.json, which is in git.
The developer-facing half of this is Secrets in a Service.