Hi All
According to the Microsoft documentation you should have an ADFS Server for each On Premise Environment.
As per my understanding, the reason is related to the workflowClientId that is an hard coded value in the \Publish-ADFSApplicationGroup.ps1 Powershell script.
Check my post as well.
Due to this reason, in order to use the same ADFS Server you have to add a new Host in the Application definition of the ADFS:
Till Soon!
According to the Microsoft documentation you should have an ADFS Server for each On Premise Environment.
As per my understanding, the reason is related to the workflowClientId that is an hard coded value in the \Publish-ADFSApplicationGroup.ps1 Powershell script.
Check my post as well.
Due to this reason, in order to use the same ADFS Server you have to add a new Host in the Application definition of the ADFS:
- AD FS Manager, Application Groups, open "Microsoft Dynamics 365 for Operations On-premises"
- Open Native application "Microsoft Dynamics 365 for Operations On-premises - Native application"
- Add Redirect URI of new environment (DNS) and select Add button to include, press OK
- Open Native application "Microsoft Dynamics 365 for Operations On-premises - Financial Reporting - Native application"
- Add Redirect URI of new environment (DNS) and select Add button to include, press OK
- Open Financial Reporting Web API "Microsoft Dynamics 365 for Operations On-premises - Financial Reporting Web API"
- In the "Relying party identifiers" section, add the new Environment Name URL with "FinancialReporting" in the prefix
- Open Web API "Microsoft Dynamics 365 for Operations On-premises - Web API"
- In the "Relying party identifiers" section, add the new Environment URL with and without "namespaces/AXSF. This is very important in order to avoid any issues with Microsoft Office addins.
Something like: - https://XXXX/namespaces/AXSF
- https://XXXX
Till Soon!