Zum Hauptinhalt springen

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​

RoleNameTypicallyWhat it does
ApplicationTISAPP*3IIS applications, Windows services, scheduled tasks
DatabaseTISDB*2SQL Server
WebTISWEB*2terminates the public host name, reverse-proxies to the application servers
Domain controllerTISDC*2Active Directory for the environment
UtilityTISUTIL1operations 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. TISAPP01 exists 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 by TISAPP03. Hardware is renewed every few years, and names are usually swapped between the 0x and 00x forms 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?

VariableValueRead by
ASPNETCORE_ENVIRONMENTFachtest, Stage or ProdASP.NET Core applications under IIS
DOTNET_ENVIRONMENTthe same valueWindows services and workers (generic host)
AZURE_TENANT_ID13d188a3-27b5-44c8-a858-a4c34d245819DefaultAzureCredential
AZURE_CLIENT_IDthe service principal for this server or environmentDefaultAzureCredential
AZURE_CLIENT_SECRETits client secretDefaultAzureCredential

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>.json overlay applied on top of appsettings.json
  • IsTisFachtest(), IsTisStage(), IsTisProduction() and IsTisTestEnvironment() from Tis.Hosting.Extensions, which is how services branch on environment
  • which Key Vault the application loads, through its own appsettings entry

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.

ProblemSymptom
Wrong environment namethe 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 secretKey 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​

EnvironmentHostAPI gatewayDeployment group
Fachtestfachtest.servicebytogether.atapi-fachtest.togethercca.comfachtest.servicebytogether.at
Stagestage.servicebytogether.atapi-stage.togethercca.comstage.servicebytogether.at
Prodwww.servicebytogether.atapi.togethercca.comwww.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​

EnvironmentKey VaultSubscriptionService principalArc + AMA
Fachtestat-tgca-tis-f-defaultTogether-Fachtestshared: fachtest-appsβœ…
Stageat-tgca-tis-s-defaultTogether-Fachtestshared: stage-apps❌
Prodat-tgca-tis-p-defaultTogether-Prodone 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. DefaultAzureCredential falls 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.json is loaded after Key Vault, and only when the environment is Development. It is the intended place for a value the development vault does not have β€” along with dotnet user-secrets, and unlike appsettings.Development.json, which is in git.

The developer-facing half of this is Secrets in a Service.