The glueckkanja Managed Foundation for Azure is 100% born in the cloud. The first step is a workshop to identify all the customer’s cloud adoption and workload requirements and map those to the Azure Cloud best practices for defining the customer’s unique Landing Zone or Zones.

After the workshop, glueckkanja team will create a unique Landing Zone Azure Blueprint using the concept of Infrastructure-as-Code or (IaC). Azure Blueprints define a repeatable set of Azure resources that implements and adheres to an organization's standards, patterns, and requirements. Azure Blueprints make it possible for development teams to rapidly build and stand up new environments and trust that they're building within organizational compliance using a set of built-in components--such as networking--to speed up development and delivery. The Landing Zone blueprint is placed in an Azure DevOps Pipeline to build or instantiate the actual Landing Zone target environment. Azure Pipelines combine continuous integration (CI) and continuous delivery (CD) to constantly and consistently test and build Landing Zone blueprints. Therefore, instead of making changes to the configuration of the actual target environment, configuration changes are first made in the Landing Zone blueprint and pushed to the actual target Landing Zone. Each Landing Zone blueprint change is version controlled.

By using IaC, cloud environments can be delivered consistently, stably, rapidly and at scale. There is no more manual configuration of the actual environment. As the customer’s needs change and as the Azure service offering changes, our Azure DevOps team keeps the Foundation for Azure and the associated blueprints up to date for you.

• Organizational Structure
• App-Zone Provisioner
• Networking
• Access Management
• Logging & Monitoring
• Security & Compliance
• Automation & Tools
• 100 % Azure native components & IaC Deployment