Okta SSO Parser Calling Incorrect Table Name

[JAK1047]

With the new Okta SSO Data Connector using Microsoft Sentinel Codeless Connector Platform Data instead of Azure Functions a backwards compatibility parser function was added:

The table called by the parser for the new Data Connector though appears to be incorrect. Calling OktaV2 for the join:

When the table name generated by the new Data Connector is OktaV2_CL:

[v-sudkharat]

Hi @JAK1047, Thanks for flagging this issue, we will investigate this issue and get back to you with some updates. Thanks!