Repository files navigation

Azure Batchis a service for running compute intensive workloads on Azure. It is a managed service for runningjobs on a pool of compute nodes. The service is designed to be highly scalable and can be used to run jobs thatrequire hundreds or thousands of compute nodes. The service is also designed to be highly customizable and can beused to run a wide variety of workloads. Getting started with Azure Batch is easy. The service can be used to run jobsin a matter of minutes. Getting a proof-of-concept (POC) that demonstrates the value of the service is relatively easy.However, taking that POC to a production deployment can be challenging especially if the deployment needs to followbest practices and security guidelines.Despite best intentions, it's not uncommon that initial designs for POCs often end up being used for production deployments.Given that, it is best to start with a system architecture that takes this into consideration.These are exactly the scenarios thatbacc is designed to address. It is designed to make it easier to develop anddeploy Azure Batch based computing infrastructure in a manner that follows best practices and security guidelines.This is part of our accelerator solution for Azure Batch intended to accelerate development of POCs as well asproduction deployments alike.

This repository is a part of our accelerator solution to make it easier for customers to deployAzure Batch workloadsin a manner that follows best practices and security guidelines. When used in conjunction with a hub deployment such asbacc-connectivity, it can be used to deploya locked down Azure Batch environment, designed for industrial use cases such as those in Financial Services (FSI).For use-cases where the complexity of a fully locked-down, hub-spoke deployment is not required, this repositorycan be used by itself.

Latest documentation is hosted onGithub Pages.

Copyright (c) Microsoft Corporation. All rights reserved.

Licensed under theMIT License

This project welcomes contributions and suggestions. Most contributions require you toagree to a Contributor License Agreement (CLA) declaring that you have the right to,and actually do, grant us the rights to use your contribution. For details, visithttps://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you needto provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow theinstructions provided by the bot. You will only need to do this once across all repositories using our CLA.

This project has adopted theMicrosoft Open Source Code of Conduct.For more information see theCode of Conduct FAQor contactopencode@microsoft.com with any additional questions or comments.