Skip to content
This repository was archived by the owner on Nov 16, 2023. It is now read-only.

Support for Recent Changes to Azure AD - Verified Domains #151

@seversen

Description

@seversen

Describe the bug
New deployments of the Azure API for FHIR no longer complete successfully because there are resources/apps that use *.azurehealthcareapis.com and this is no longer valid per: https://docs.microsoft.com/en-us/azure/active-directory/develop/reference-breaking-changes#appid-uri-in-single-tenant-applications-will-require-use-of-default-scheme-or-verified-domains

To Reproduce
Steps to reproduce the behavior, including exact commands you are running:

  1. Follow normal environment setup steps.
  2. Run .\Create-FhirServerSamplesEnvironment.ps1 -EnvironmentName -UsePaaS $true
  3. See error

Expected behavior
The entire sample environment should be provisioned. It only provisions the Key Vault and then throws an error similar to this:

Error occurred while executing NewApplication Code: Request_BadRequest Message: Values of identifierUris property must use a verified domain of the organization or its subdomain: 'https://example123.azurehealthcareapis.com' Details: PropertyName - identifierUris, PropertyErrorCode - HostNameNotOnVerifiedDomain, HostName - https://example123.azurehealthcareapis.com HttpStatusCode: BadRequest HttpStatusDescription: Bad Request HttpResponseStatus: Completed

This issue was also reported in a different GitHub project: https://github.com/Azure/azure-docs-powershell-azuread/issues/724

Are there any plans to address this? As far as I can tell, this project no longer works at all because of the new restrictions.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions