--- title: Workforce Use Cases description: Authenticating Azure AD tenants who don't have their own Azure account component: solution-guides page_id: solution-guides:workforce_use_cases:htg_workforce canonical_url: https://docs.pingidentity.com/solution-guides/workforce_use_cases/htg_workforce.html revdate: January 19, 2024 --- # Workforce Use Cases | Use case | Description | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [Authenticating Azure AD tenants who don't have their own Azure account](htg_authn_azure_ad_tenants.html) | Create a PingFederate workflow to authenticate users from different Microsoft tenants. | | [Configuring adaptive authentication in PingFederate](htg_config_adaptive_authn_pf.html) | This document explains the conceptual information behind network-based adaptive authentication. It also provides instructions for creating a new selector and configuring an authentication policy to enable adaptive authentication. | | [Configuring an Active Directory datastore for PingFederate](htg_config_ad_datastore_pf.html) | In PingFederate, establish an Active Directory datastore connection for retrieving user attributes for outbound connections. | | [Configuring a SAML application](htg_config_saml_app.html) | Configure a SAML application in PingFederate, PingOne, and PingOne for Enterprise. | | [Connecting PingFederate to a Microsoft SQL JDBC datastore with Windows authentication](htg_connect_pf_to_ms_sql_jdbc_datastore.html) | Create a Microsoft SQL server Java Database Connectivity (JDBC)-connected datastore in PingFederate and configure it for Windows authentication. | | [Connecting PingFederate with Yahoo through OIDC](htg_connect_pf_with_yahoo_through_oidc.html) | Learn how to connect PingFederate with your Yahoo developer account using OpenID Connect (OIDC). | | [Delegating all authentication to an external IdP](htg_delegate_authn_to_external_idp.html) | PingOne provides an authentication policy step that allows you to make an external identity provider (IdP) part of a PingOne authentication policy or delegate all authentication to that external IdP. | | [Enabling SLO for a PingAccess-protected application using PingFederate](htg_enable_slo_for_pa_protected_app_using_pf.html) | Learn how to require a sign off of a PingAccess-protected application with PingFederate acting as token provider. | | [Integrating Pulse Connect Secure with PingFederate](htg_integrate_pulse_connect_secure_with_pf.html) | Learn how to integrate Pulse Connect Secure with PingFederate for single sign-on (SSO). | | [Protecting a web application with PingAccess using PingFederate as the token provider](htg_protect_web_app_with_pa_using_pf_as_token_provider.html) | Configure a proof of concept to protect a web application from unwanted access using PingAccess with PingFederate as the token provider. | | [Protecting your VPN with PingID MFA](htg_protect_vpn_with_pid_mfa.html) | To improve network security posture and provide a true MFA experience to network resources, add PingID multi-factor authentication (MFA) to your VPN authentication ceremony. | | [Setting up a login form that validates credentials against AD in PingFederate](htg_set_up_login_form_validating_creds_with_ad_pf.html) | Configure a login form in PingFederate that validates credentials against Active Directory (AD). | | [Setting up an agent in PingAccess](../customer_use_cases/htg_agent_setup_pa.html) | Learn how to set up an agent integration for PingAccess applications. | | [Setting up an authentication flow that includes MFA (PingFederate and PingID)](htg_set_up_authn_flow_mfa_pf_pid.html) | This configuration creates a service provider (SP) connection with a multi-factor authentication (MFA) flow using PingFederate and PingID. | | [Setting up an authentication flow that includes MFA (PingOne for Enterprise and PingID)](htg_set_up_authn_flow_mfa_p14e_pid.html) | You can create an authentication flow that uses multi-factor authentication (MFA) with PingOne for Enterprise and PingID. | | [Setting up an OIDC application in PingFederate](../customer_use_cases/htg_oidc_app_setup_pf.html) | Create a new OAuth or OpenID Connect (OIDC) application in PingFederate. | | [Setting up and testing a custom authentication policy](htg_set_up_test_custom_authn_policy.html) | Authentication policies are used in PingFederate to implement complex authentication requirements. This document explains how to create a new custom authentication policy in PingFederate, and then test the policy. | | [Setting up Kerberos authentication in PingFederate](htg_set_up_kerberos_authn_pf.html) | Set up a Kerberos authentication adapter in PingFederate for a seamless user authentication experience from a Windows machine to your applications. | | [Setting up password recovery in PingFederate](htg_pf_password_recovery_setup.html) | Learn how to set up PingFederate for self-service password reset and account recovery through an HTML Form Adapter. | | [Setting up passwordless authentication in PingOne](htg_p1_passwordless_authn_setup.html) | Learn how to set up passwordless authentication and eliminate the need for your users to enter a password. Passwordless authentication is a quick and easy configuration where end users sign on with a paired multi-factor authentication (MFA) device. | | [Setting up PingFederate as a FedHub](htg_set_up_pf_as_fedhub.html) | Configuring PingFederate as an identity bridge or FedHub (SAML Chaining) allows you to manage external identities and facilitate access to applications across the enterprise community. | | [Setting up your PingOne Dock](htg_p1_dock_setup.html) | The PingOne Dock gives your users one-click, single sign-on (SSO) access to the applications and other service providers (SPs) you authorize them to use. | | [Updating a PingOne for Enterprise verification certificate on an unmanaged PingFederate identity bridge](htg_update_p14e_verification_cert_unmangaged_pf_identity_bridge.html) | If you use an unmanaged manual PingFederate connection as the identity provider (IdP) for PingOne for Enterprise, and your certificate is about to expire, you must update your signing certificate in PingFederate and your verification certificate in PingOne for Enterprise. |