Skip to content

409 Request_MultipleObjectsWithSameKeyValue when updating IssuerUri #3625

Closed

Description

@frhuamzn

Describe the bug

Update-MgBetaDomainFederationConfiguration returns 409 Request_MultipleObjectsWithSameKeyValue when setting an IssuerUri that is already used by another domain's federation configuration in the same tenant. This uniqueness constraint on IssuerUri is not documented on the API reference page.

Expected behavior

The API documentation does not mention that IssuerUri must be globally unique across all federated domains in a tenant. This constraint should be documented.

How to reproduce

  1. Successfully create federation config on contoso.com with IssuerUri A.

  2. Attempt to update it to use the same IssuerUri already assigned to fabrikam.com:

    Update-MgBetaDomainFederationConfiguration -DomainId "contoso.com" -InternalDomainFederationId $fedId
    -IssuerUri "https://idp.example.com/shared-issuer"

Result

409 Request_MultipleObjectsWithSameKeyValue

SDK Version

2.37.0

Latest version known to work for scenario above?

N/A

Known Workarounds

Use a new Issuer URI

Debug output

Click to expand log ``` 409 Request_MultipleObjectsWithSameKeyValue
</details>


### Configuration

N/A

### Other information

N/A

Activity

  1. gavinbarron commented on Jun 1, 2026

    @gavinbarron
    Member

    Please provide the output of the cmdlet when run with the -Debug flag
    This helps us route this issue internally.

  2. microsoft-github-policy-service commented on Jun 5, 2026

    @microsoft-github-policy-service
    Contributor

    This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions