Hello Aravind,
I was just looking over this and to explain to everyone, you're wondering if the method described in this document could be applicable to a PingOne/PingIdentity implementation: https://learn.microsoft.com/en-us/azure/active-directory-b2c/identity-provider-azure-ad-multi-tenant?pivots=b2c-custom-policy#restrict-access.
While I don't have as much familiarity with Ping, reviewing the documentation on the B2C side: https://learn.microsoft.com/en-us/azure/active-directory-b2c/openid-connect-technical-profile#metadata
This indicates that this can be used to support any multi-tenant identity provider such as Azure AD. Theoretically, this would be doable with PingOne, however I would make sure you have a common Metadata endpoint that can be used across each PingOne tenant, similar to how AAD does this, and then ensure that you have the ValidTokenIssuerPrefixes enabled and pointing to the right PingOne issuer values, this could all theoretically work, however I'm not very familiar with the PingOne/PingIdentity IdP so there may be a limiting factor there.