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
-
Successfully create federation config on contoso.com with IssuerUri A.
-
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
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
Successfully create federation config on contoso.com with IssuerUri A.
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