Forum Discussion
AAD Connect + Ping Federate
Anyone have insight into the capabilities this integration will bring and/or timeline for it?
Noticed the announcement about Ping Access today but more interested in the Ping Federate side. Here is the article with initial reference:
I would recommend connecting with Ping Identity sales team. Ping Access is not seen as an upgrade or instead of Ping Federate - they play different roles in your access strategy but it would be wrong of me to try and explain that.
In Azure AD there is one component that does all the authentication, federation and sso capabilities similar to what Ping Fed/ADFS does on premises and then the Application Proxy is about taking an internal web application and making this available to end users that are outside the network.
Brjann
- EricStarkerCommunity Manager
Great question! Have you looked at this yet?
https://ping.force.com/Support/PingIdentityArticle?id=kA340000000PMraCAG
- BrjannBrekkanMicrosoft
The integration with Ping is really around Ping Access and we released the preview together with Ping just a few days ago. https://blogs.technet.microsoft.com/enterprisemobility/2017/03/22/pingaccess-for-azure-ad-the-public-preview-is-being-deployed/
The Ping Federate integration is purely a feature that will allow Azure AD Connect to launch the setup of Ping Federate. Just like with AD FS there is no integration needed with Azure AD Connect after the initial setup. Ping Federate has been a supported Azure AD compatible federation provider for many years and that doesn't change with this.
Brjann Brekkan
- Azure AD Program Manager
- Jerry MeyerIron Contributor
We have Ping Federate as replacement for ADFS in place Only this is not a new configuration with Ping Access. I am also really interested in this case, there could be a good reason to upgrade to Ping access.
Regarding the configuration of Ping federation this is almost identical to the configuration of ADFS 2.0.