SSO for Azure AD domain joined machines - Sign in usng ActiveDirectory button is not present

[ErickEspinosa]

Per Microcrosotf recommendation that Azure AD join should be the first choice for new devices, we have deployed new machines to our RPA team, Microsoft indicates that SSO to on-premise resources (like Blue Prism) can still authenticate.

https://learn.microsoft.com/en-us/azure/active-directory/devices/plan-device-deployment#azure-ad-join

These machines are currently not able to SSO into BluePrism [Sign in usng ActiveDirectory button is not present], after working with the BP support team it was indicated that BluePrism is looking for the domain once is executed and not finding the Azure AD machine in the domain. 

type -AssemblyName System.DirectoryServices
$domain=[System.DirectoryServices.ActiveDirectory.Domain]::GetComputerDomain()
Write-Host "Current Domain: $($domain.Name)"

We need the BP app to be more flexible as more and more companies are moving towards Azure AD joined machines.

[BUL_LA]

Hello has this been solved ?
We are facing the same issue with a Windows 11, upgrade and the company starting to use Azure. The button Active Directory is not present as well.

Thanks

[Ninoseki]

Hello @BUL_LA ,

Unfortunately, Blue Prism Enterprise does not currently support Azure AD (Microsoft Entra ID).
Does Blue Prism Enterprise support Azure Entra ID? (support.blueprism.com)

As more organizations are gradually shifting to use Microsoft Entra ID exclusively—without deploying on-premises Active Directory servers—we sincerely hope Blue Prism will prioritize support for Entra ID in the near future.

Regards,
Yusuke Ninoseki