The Microsoft Graph Bicep extension enables customers to manage a limited set of Identity/Graph resources (Microsoft Entra ID, formerly known as Azure AD) in Bicep templates (alongside Azure resources) through native Microsoft Graph APIs. This unblocks Infrastructure-as-Code/DevOps outcomes for Azure customers and will close a long-standing platform gap and pain-point.
Customers can then use Azure CLI or Azure PowerShell to deploy Bicep templates and their set of Microsoft Azure and/or Microsoft Entra ID resources.
The releases page provides details on the supported Microsoft Graph Bicep types and limitations for the public preview.
To get going with the public preview, start with the Bicep templates for Microsoft Graph resources public documentation.
This project welcomes contributions and suggestions. Most contributions require you to agree 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, visit https://cla.opensource.microsoft.com.
When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.
See Contributing to Microsoft Graph Bicep extension for information on contributing (or fixing) examples, new types requests, feature suggestions, or bug reports on functionality or existing quickstart samples.
Note: Contribution to new Bicep types is limited to feature requests via GitHub Issues at this point. We encourage you to utilize the issue type designated for requesting new Graph Bicep types. Your input is valuable and helps us prioritize updates with the API service teams to enhance Bicep support.
This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.