Nordlicht Reisen GmbH (R-01) has the travel assistant audited before launch. The auditors want to know where keys are stored (R-07: nowhere), who may do what, and whether the Foundry project can be reached from the internet. According to E-08 the exercises run with a public endpoint and Entra sign-in; the private network is a design with a Bicep sketch, compiled and not deployed. You do not need an Azure account. Cost drivers of the design: private endpoints, the resources of the standard setup for agents (storage, search, Cosmos DB) and self-hosted runners; prices are on the pricing pages.
Prior knowledge. Managed identity, Key Vault and least privilege are taught in "K3, lessons 3.3.1, 3.3.2 and 3.3.5", firewalls and NSGs in "K3, module 3.0". You interpret Azure RBAC following "AZ-104, lesson 1.3", private endpoints and service endpoints following "AZ-104, lesson 4.4", DNS following "AZ-104, lesson 4.5"; identity and network in the design in "AZ-305, lessons 1.2 and 6.3". Signing in without keys is shown in "AI track, lesson T10.1", rights per tool in "AI track, lesson T8.3". Only the Foundry view applies here.
The requirement
| No. | Requirement | Type | Measure | Weight | Source |
|---|---|---|---|---|---|
| 1.4-01 | No key in code, configuration or pipeline (R-07). | R | 0 keys | Must | Security |
| 1.4-02 | People sign in with Entra ID (R-07). | R | 0 local accounts | Must | Security |
| 1.4-03 | The application calls agents but does not manage them. | R | rights only for the call | Must | Security |
| 1.4-04 | The pipeline creates agent versions but does not assign roles. | R | 2 separate identities | Must | Security |
| 1.4-05 | In production the project can be reached only from the own network (design, E-08). | R | public access off | Should | Auditors |
| 1.4-06 | Only the platform team changes deployments and deployment types. | R | 1 group | Should | Platform |