Okta, Microsoft Entra ID and several other cloud identity services do not consume InCommon metadata, nor can they use it as a basis for trust. Further, many of these types of services do not allow you to set your own entityID, which will cause problems (or complete failure) in trying to register your metadata with InCommon. Thus, direct use of these services with InCommon is not supported. There are ways to make them work, but these involve either running your own Identity Provider (such as Shibboleth IdP) and connecting it to LDAP endpoints within these services, or more commonly, setting up a proxy (on your own or provided by a service such as Cirrus Identity Bridge).
We have some resources available that can guide your decisions on how to proceed. We recommend working with an InCommon Catalyst partner such as Cirrus Identity or Unicon to have them run and IdP on your behalf, which can backend into Entra, or to run a proxy product like Cirrus Bridge. You would work with your proxy partner to retrieve metadata via MDQ.
https://spaces.at.internet2.edu/display/federation/enable-user-access-to-federated-resources
Microsoft has published additional information on this at: https://learn.microsoft.com/en-us/entra/architecture/multilateral-federation-introduction