Building with continual iteration – Enterprise Design Considerations
Building cloud solutions can be a complex process, especially when trying to build for large enterprises. One option when first developing your cloud adoption is to fully define and build your management tooling upfront; however, this can take some time and delay your ability to realize the cost benefits. Another approach is to build a …
Building with continual iteration – Enterprise Design ConsiderationsRead More
Identity – Enterprise Design Considerations
How your users are authorized and authenticated is often one of the first considerations. Will you use a single Active Directory for all users? Will you have multiple directories for different environments? Will you combine internal users and external clients using guest accounts or separate them? For example, Azure offers B2B and B2C integrations that …
Optimizing costs – Enterprise Design Considerations
Cloud solutions can be built with incredible flexibility around the resources they consume. We can create systems that dynamically respond to usage so that they scale automatically as needed. Serverless options also allow for solutions that cost near zero when not being used. By way of an example, services such as Azure functions are billed …
Optimizing costs – Enterprise Design ConsiderationsRead More
Looking at process differences – Enterprise Design Considerations
In the previous chapter, we began looking at Azure design from an everyday working perspective, looking at examples of how to engage with customers, and then gather, map, and document requirements. In this final chapter, we complete the beyond the exam theme by looking at what specific considerations we need to make when designing enterprise …
Looking at process differences – Enterprise Design ConsiderationsRead More
Mapping requirements – Engaging with Real-World Customers
It may seem obvious, but we need to ensure requirements are recorded and referred to during the projects life cycle. Especially with agile projects, requirements can change through the project, and any such decisions need to be logged and updated along with the reasons why they were changed. There are specialist tools available to help …
Mapping requirements – Engaging with Real-World CustomersRead More
Azure Artifacts – Scripted Deployments and DevOps Automation
In software development, it is common to want to share code or even pre-built components that execute specific tasks. For example, if a developer has built a function that performs a complex calculation, you may wish to share that with other developers as an artifact so that they can re-use it. This is different from …
Azure Artifacts – Scripted Deployments and DevOps AutomationRead More
Azure Pipelines – Scripted Deployments and DevOps Automation
We can build and deploy components in Azure from ARM templates using PowerShell or the Azure CLI by using the New-AzResourceGroupDeployment or az deployment group create commands. Azure Pipelines provides on-demand VM nodes with the necessary tooling installed to perform our deployments. In other words, rather than running the required PowerShell or Azure CLI scripts …
Azure Pipelines – Scripted Deployments and DevOps AutomationRead More
Azure Repos – Scripted Deployments and DevOps Automation
Azure Repos allows you to control and manage code changes by enforcing versioning and tracking of changes across files. Code is stored in a repository and repositories use branches to provide an additional layer of management. Each repository has at least one branch; by default, this is called the master branch. When a user wishes …
Azure Repos – Scripted Deployments and DevOps AutomationRead More
Understanding ARM templates – Scripted Deployments and DevOps Automation-1
Just as other tools are simply wrappers for the Azure REST APIs, everything that is built in Azure is defined as an ARM template. Whether you create a service through the Azure portal, PowerShell, REST APIs, or the CLI, ultimately that service is described within an ARM template. An ARM template is a JSON-based text …
Understanding ARM templates – Scripted Deployments and DevOps Automation-1Read More
Choosing between PowerShell and the Azure CLI – Scripted Deployments and DevOps Automation
When we start to consider automating the deployment and management of resources in Azure, the first option would be using the command line, and here we then have two further options: PowerShell and the Azure CLI. PowerShell and the CLI are very similar: they both run from a command prompt, they both allow access to …
Choosing between PowerShell and the Azure CLI – Scripted Deployments and DevOps AutomationRead More
