Azure / appservice-landing-zone-accelerator

The Azure App Service landing zone accelerator is an open-source collection of architectural guidance and reference implementation to accelerate deployment of Azure App Service at scale.
https://build.microsoft.com/en-US/sessions/58f92fab-3298-444d-b215-6b93219cd5d7?source=sessions
MIT License
200 stars 95 forks source link

Chore: Change Azure AD refs to Microsoft Entra #204

Closed ibersanoMS closed 3 months ago

ibersanoMS commented 4 months ago

Description

Pipeline references

For module/pipeline changes, please create and attach the status badge of your successful run.

Pipeline

Type of Change

Please delete options that are not relevant.

Checklist

github-actions[bot] commented 4 months ago

Terraform Plan failed

Plan Error Output ``` Error: Error ensuring Resource Providers are registered. Terraform automatically attempts to register the Resource Providers it supports to ensure it's able to provision resources. If you don't have permission to register Resource Providers you may wish to use the "skip_provider_registration" flag in the Provider block to disable this functionality. Please note that if you opt out of Resource Provider Registration and Terraform tries to provision a resource from a Resource Provider which is unregistered, then the errors may appear misleading - for example: > API version 2019-XX-XX was not found for Microsoft.Foo Could indicate either that the Resource Provider "Microsoft.Foo" requires registration, but this could also indicate that this Azure Region doesn't support this API version. More information on the "skip_provider_registration" flag can be found here: https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs#skip_provider_registration Original Error: Cannot register providers: Microsoft.SignalRService, Microsoft.DataFactory. Errors were: Cannot register provider Microsoft.SignalRService with Azure Resource Manager: unexpected status 403 with error: AuthorizationFailed: The client '6f1b60ca-5362-4f06-bc90-0ab4bb178f8a' with object id '6f1b60ca-5362-4f06-bc90-0ab4bb178f8a' does not have authorization to perform action 'Microsoft.SignalRService/register/action' over scope '/subscriptions/864eb9d0-e9c4-4d6b-bf11-bd4cfde05e81' or the scope is invalid. If access was recently granted, please refresh your credentials.. Cannot register provider Microsoft.DataFactory with Azure Resource Manager: unexpected status 403 with error: AuthorizationFailed: The client '6f1b60ca-5362-4f06-bc90-0ab4bb178f8a' with object id '6f1b60ca-5362-4f06-bc90-0ab4bb178f8a' does not have authorization to perform action 'Microsoft.DataFactory/register/action' over scope '/subscriptions/864eb9d0-e9c4-4d6b-bf11-bd4cfde05e81' or the scope is invalid. If access was recently granted, please refresh your credentials.. with provider["registry.terraform.io/hashicorp/azurerm"], on main.tf line 17, in provider "azurerm": 17: provider "azurerm" { ``` *Pusher: @ibersanoMS, Action: `pull_request`, Working Directory: `scenarios/secure-baseline-multitenant/terraform/hub`, Workflow: `Scenario 1: Terraform Multi-Tenant ASEv3 Secure Baseline`*
github-actions[bot] commented 4 months ago

Terraform Plan failed

Plan Error Output ``` Error: Error ensuring Resource Providers are registered. Terraform automatically attempts to register the Resource Providers it supports to ensure it's able to provision resources. If you don't have permission to register Resource Providers you may wish to use the "skip_provider_registration" flag in the Provider block to disable this functionality. Please note that if you opt out of Resource Provider Registration and Terraform tries to provision a resource from a Resource Provider which is unregistered, then the errors may appear misleading - for example: > API version 2019-XX-XX was not found for Microsoft.Foo Could indicate either that the Resource Provider "Microsoft.Foo" requires registration, but this could also indicate that this Azure Region doesn't support this API version. More information on the "skip_provider_registration" flag can be found here: https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs#skip_provider_registration Original Error: Cannot register providers: Microsoft.SignalRService, Microsoft.DataFactory. Errors were: Cannot register provider Microsoft.SignalRService with Azure Resource Manager: unexpected status 403 with error: AuthorizationFailed: The client '6f1b60ca-5362-4f06-bc90-0ab4bb178f8a' with object id '6f1b60ca-5362-4f06-bc90-0ab4bb178f8a' does not have authorization to perform action 'Microsoft.SignalRService/register/action' over scope '/subscriptions/864eb9d0-e9c4-4d6b-bf11-bd4cfde05e81' or the scope is invalid. If access was recently granted, please refresh your credentials.. Cannot register provider Microsoft.DataFactory with Azure Resource Manager: unexpected status 403 with error: AuthorizationFailed: The client '6f1b60ca-5362-4f06-bc90-0ab4bb178f8a' with object id '6f1b60ca-5362-4f06-bc90-0ab4bb178f8a' does not have authorization to perform action 'Microsoft.DataFactory/register/action' over scope '/subscriptions/864eb9d0-e9c4-4d6b-bf11-bd4cfde05e81' or the scope is invalid. If access was recently granted, please refresh your credentials.. with provider["registry.terraform.io/hashicorp/azurerm"], on main.tf line 17, in provider "azurerm": 17: provider "azurerm" { ``` *Pusher: @ibersanoMS, Action: `pull_request`, Working Directory: `scenarios/secure-baseline-multitenant/terraform/hub`, Workflow: `Scenario 1: Terraform Multi-Tenant ASEv3 Secure Baseline`*