{"id":457,"date":"2024-07-29T07:44:33","date_gmt":"2024-07-28T21:44:33","guid":{"rendered":"https:\/\/www.cloudproinc.com.au\/?p=457"},"modified":"2024-07-29T07:44:37","modified_gmt":"2024-07-28T21:44:37","slug":"streamlining-entra-id-app-registrations-with-azure-bicep","status":"publish","type":"post","link":"https:\/\/cloudproinc.com.au\/index.php\/2024\/07\/29\/streamlining-entra-id-app-registrations-with-azure-bicep\/","title":{"rendered":"Streamlining Entra ID App Registrations with Azure Bicep"},"content":{"rendered":"\n

In this Azure Bicep and Entra ID, we will show you how to create an Entra ID App Registration using Azure Bicep.

<\/p>\n\n\n\n\n\n\n\n

Entra ID (formerly Azure Active Directory) is Microsoft’s Azure and Microsoft 355 authentication and authorization service, handling all login events to both services. <\/p>\n\n\n\n

App Registrations in Entra ID are service accounts used inside applications that utilize the Azure SDK to programmatically access and create Azure Services, including Microsoft Graph Security API<\/a>.<\/p>\n\n\n\n

Creating and managing App Registrations can be overwhelming in a multi-tenant environment where hundreds of accounts are needed for each customer. <\/p>\n\n\n\n

For that reason, Azure Bicep has created the Microsoft Graph extension, which allows us to create App Registrations using Bicep. <\/p>\n\n\n\n

Streamlining Entra ID App Registrations with Azure Bicep<\/h2>\n\n\n\n

The extension is still in preview mode, so you must meet the prerequisites before trying to create an app registration. <\/p>\n\n\n\n

prerequisites <\/h2>\n\n\n\n

First, we need to ensure that the bicep version we are using is 0.29 or above. To check which Bicep version is installed on your machine, run the following command.<\/p>\n\n\n\n

bicep --version<\/code><\/pre>\n\n\n\n
The output should look like this.<\/p>\n\n\n\n
Bicep CLI version 0.29.47 (132ade51bc)<\/code><\/pre>\n\n\n\n
If you don’t have the right version, update Bicep using the following command (Windows only).<\/p>\n\n\n\n
winget install -e --id Microsoft.Bicep<\/code><\/pre>\n\n\n\n
Create a Bicep Config file <\/h2>\n\n\n\n
Since we are using a preview feature, we need to create a bicepconfig.json file with the following code in the same directory of our Bicep main file.<\/p>\n\n\n\n
{\n  \"experimentalFeaturesEnabled\": {\n      \"extensibility\": true\n  }\n}<\/code><\/pre>\n\n\n\n
Create an App Registration<\/h2>\n\n\n\n
Finally, we can create an App Registration using the following configuration. Change the display and unique name of your app and start the deployment.<\/p>\n\n\n\n
extension microsoftGraph\n\nresource application 'Microsoft.Graph\/applications@v1.0' = {\n  displayName: 'Extention Attributes App'\n  uniqueName:  'ExtentionAttributesapp'\n}<\/code><\/pre>\n\n\n\n
Run the following Azure PowerShell cmdlet to create the App Registration in Entra ID.<\/p>\n\n\n\n
New-AzResourceGroupDeployment -ResourceGroupName \"bicep-lab\" -TemplateFile .\\main.bicep <\/code><\/pre>\n\n\n\n
About Azure Bicep<\/h2>\n\n\n\n
Azure Bicep is a specific domain language (DSL) used for infrastructure-as-code (iac) deployments in Azure only. Unlike other tools like Terraform, Bicep offers access to the latest Azure API from day one. By default (the only option), Bicep saves the deployment’s state files in Azure and does not use a local copy. To learn more about Bicep, visit this link<\/a>.<\/p>\n\n\n\n
Similar Articles <\/h2>\n\n\n\n