Connector returned null partitions on account aggregation (Azure AD / Entra)

Identity Security Cloud (ISC) ISC Discussion and Questions
, ,
1

When enabling partitioning for the Azure AD connector, the aggregation returns the error ‘connector returned null partitions’

Have attempted several different partition filters and increased the number of threads, see a few samples below. Are there any other configurations that can be set to ensure the connector does not return null partitions?

"userPartitions": [
            "accountEnabled eq true",
            "accountEnabled eq false"
        ]

"userPartitions": [
            "startswith(displayName,'.') or startswith(displayName,'--') or startswith(displayName,'1') or startswith(displayName,'2') or startswith(displayName,'3') or startswith(displayName,'4') or startswith(displayName,'5') or startswith(displayName,'6') or startswith(displayName,'7') or startswith(displayName,'8') or startswith(displayName,'9') or startswith(displayName,'0')",
            "startswith(displayName,'A')",
            "startswith(displayName,'B')",
            "startswith(displayName,'C')",
            "startswith(displayName,'D')",
            "startswith(displayName,'E')",
            "startswith(displayName,'F')",
            "startswith(displayName,'G')",
            "startswith(displayName,'H')",
            "startswith(displayName,'I')",
            "startswith(displayName,'J')",
            "startswith(displayName,'K')",
            "startswith(displayName,'L')",
            "startswith(displayName,'M')",
            "startswith(displayName,'N')",
            "startswith(displayName,'O')",
            "startswith(displayName,'P')",
            "startswith(displayName,'Q')",
            "startswith(displayName,'R')",
            "startswith(displayName,'S')",
            "startswith(displayName,'T')",
            "startswith(displayName,'U')",
            "startswith(displayName,'V')",
            "startswith(displayName,'W')",
            "startswith(displayName,'X')",
            "startswith(displayName,'Y')",
            "startswith(displayName,'Z')"
        ]

Screenshot 2024-07-02 at 11.04.34 AM
Screenshot 2024-07-02 at 11.04.34 AM1328×522 30.4 KB

2

Hi @margocbain,

I think not existing a setup on the connector for this, for me the solution is regulate the conditions of partitioning, creating a logic where you are sure to have almost one object for each partition.

ps Have you set 27 threads on va?

1 Like
3

After re-creating the source and applying the same configurations, the partitioning works as expected. I suspect that the issue may have been related to a temporary e-fix that was applied to the connector for a separate issue and may have impacted partitioning. Applying even direct partitions to where we were sure we had at least 1 object per partition and matching partitions still produced the issue.
Thank you!

4

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.