Entra ID - Provisioning & Identity Synchronization

Question

Entra ID - Provisioning & Identity Synchronization

Shree Varshan G 40

Dear Microsoft Support Team,

I am reaching out to request clarification on the availability of SCIM 2.0 enterprise extension attributes across different Microsoft Entra ID licensing tiers.

Background: We are implementing SCIM provisioning from Entra ID to our application and need to understand the licensing requirements for using enterprise extension attributes defined in the SCIM 2.0 standard (RFC 7643).

Specific Questions:

Enterprise Extension Attribute Availability:
- Are the SCIM enterprise extension attributes (e.g., urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:department, employeeNumber, organization, division, costCenter, manager) available across all Entra ID license tiers (Free, Premium P1, Premium P2)?
- Or are these attributes restricted to specific license plans?
Outbound SCIM Provisioning:
- For outbound provisioning from Entra ID to third-party SaaS applications, what are the exact licensing requirements to: a) Use core SCIM user schema attributes? b) Use SCIM enterprise extension attributes? c) Configure custom attribute mappings for these enterprise extension fields?
Default Attribute Mappings:
- Are enterprise extension attributes (like department, employeeNumber, organization) included in the default attribute mappings for SCIM provisioning, regardless of license tier?
- Do we need any specific license to map Entra ID attributes (e.g., companyName → urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:Organization)?
Documentation Reference:

Could you please provide official documentation that clearly outlines which SCIM schema attributes are available per license tier?

What We've Found: Based on our research, we understand that basic user provisioning via SCIM is available in the Free tier, but we want to confirm that the enterprise extension attributes are also included or if they require Premium licensing.

Expected Outcome: We need confirmation on what Entra ID license tier supports the full use of SCIM enterprise extension attributes or if we need to upgrade to Premium P1/P2.

Thank you for your assistance. Please let me know if you need any additional information to help clarify this matter.

VEMULA SRISAI 13,890 Reputation points Microsoft External Staff Moderator

2026-01-08T15:03:21.62+00:00
Hello Shree Varshan G,

It definitely sounds like you're diving deep into SCIM provisioning and trying to nail down the specifics of SCIM 2.0 enterprise extension attributes across Microsoft Entra ID licensing tiers. Let's break down your questions:

1. Enterprise Extension Attribute Availability

Are SCIM enterprise extension attributes available across all license tiers? Generally, enterprise extension attributes like urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:department, employeeNumber, organization, and others tend to require at least a Premium P1 license to access. The Free tier usually has limitations on advanced features, so you might need to upgrade if these attributes are critical for your implementation.
2. Outbound SCIM Provisioning Licensing

Licensing requirements for outbound provisioning:

Core SCIM user schema attributes: Typically available in the Free tier.

SCIM enterprise extension attributes: Generally require a Premium P1 or P2 license.

Configuring custom attribute mappings for these enterprise extension fields: This might also require a Premium license, specifically for the flexibility and additional mapping capabilities.

3. Default Attribute Mappings

Are enterprise extension attributes included in default mappings? Default attribute mappings often include basic attributes across all tiers. More detailed enterprise extension mappings may be limited to higher tiers, suggesting you might need to check for specific requirements if you're looking to integrate these attributes.

Specific license for mapping Entra ID attributes? If you want to map attributes like companyName to enterprise extension attributes, this usually requires a Premium P1/P2 license.

4. Documentation Reference

To get the most accurate information regarding which SCIM schema attributes are included per license tier, I'd recommend checking out the official Microsoft documentation available here: Microsoft Entra User Provisioning and Synchronization.
Follow-Up Questions

To better assist you, here are a few follow-up questions:

What specific version of SCIM are you targeting for your application?

Are there particular attributes among the enterprise extension attributes that are more critical for your implementation than others?

Can you clarify whether you're planning to perform just outbound provisioning, or will you need attribute synchronization as well?

Are you already using any specific Entra ID tier, or are you considering which tier to subscribe to?

Hope this gives you a solid starting point! Let me know if you have more questions or need further details on anything.

References

What is Microsoft Entra Cloud Sync?

What is the Microsoft Entra provisioning agent?

Troubleshoot Cloud Sync - Object Synchronization Problems

Microsoft Entra User Provisioning and Synchronization

Compare Active Directory to Microsoft Entra ID
Shree Varshan G 40 Reputation points

2026-01-09T07:26:54.9366667+00:00
We currently have Azure AD Premium P2 licenses, and we need to understand whether our customers will be able to use SCIM provisioning to sync their company name.

We are planning to map the company name using the Enterprise Organization attribute. However, before proceeding, we need clarification on the following:

If the enterprise attribute is not available for all plans, we need an alternative approach that ensures the companyName is synced consistently across all plans.

Additionally, we would like to confirm whether the permission to edit the “Edit attribute list for customappsso” setting is available in Premium plans, or if it is limited to higher-tier licenses.

This information will help us decide the correct attribute mapping strategy going forward.
VEMULA SRISAI 13,890 Reputation points Microsoft External Staff Moderator

2026-01-09T18:25:39.3533333+00:00
Shree Varshan G Thank you for your follow-up.

Enterprise Attribute Availability: The SCIM enterprise extension attributes (including organization) are supported for outbound provisioning across all Microsoft Entra ID license tiers, including Free. Since you have Premium P2, you can map companyName to urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:organization without any restrictions. Customers on Free tier can also use this mapping.

Alternative Approach: There is no license-based limitation for using enterprise attributes. If you prefer, you can also map companyName to a core SCIM attribute (e.g., displayName) as a fallback, but this is not required for license reasons.

Edit Attribute List for customappsso: The ability to edit attribute mappings (including adding enterprise attributes) is available for all tiers. Premium plans do not restrict this; they only add advanced provisioning features like assignment-based scoping.

References:

Customize attribute mappings for SaaS apps
Shree Varshan G 40 Reputation points

2026-01-10T11:07:46.76+00:00

Microsoft Entra NEVER sends cleared enterprise attributes in PATCH

Not "", not null, not Remove — it simply omits them.

is this true . i need to track the companyName if it is cleared and having values as well i tried after clearing then it is not sended from entra

how this can be fixed any workaround or something im missing
VEMULA SRISAI 13,890 Reputation points Microsoft External Staff Moderator

2026-01-20T17:58:00.3066667+00:00

Shree Varshan G ,Microsoft Entra does not send cleared enterprise attributes in PATCH—cleared values are simply omitted, not sent as null, "", or Remove. This is expected behavior, and the SCIM service treats “missing attribute” as “attribute was cleared.” To track deletes, your SCIM API must interpret omitted fields as removals. There is no Entra-side fix; the workaround is handling this logic in your SCIM endpoint.
Shree Varshan G 40 Reputation points

2026-01-29T09:42:21.0666667+00:00
i found this in google

Enterprise extension attributes—such as department, employeeNumber, and organization (part of the urn:ietf:params:scim:schemas:extension:enterprise:2.0:User schema)—are generally not available in the Microsoft Entra ID Free tier for outbound SCIM provisioning. These extended attributes typically require at least a Premium P1 license.

Key points regarding attribute availability in Entra:

SCIM Provisioning (Outbound): While core user attributes are supported, Enterprise Extension Attributes often require a premium license.

Entra Connect Sync (Hybrid): Basic synchronization of core Active Directory attributes is included in the free tier, but specialized enterprise extension mappings may be restricted.

Alternative: If you are using Entra ID Free for SaaS provisioning, you may be limited to core attributes and cannot use custom enterprise mappings.

the enterprise attributes are available only on premium p1/p2 ? but you are telling

Enterprise Attribute Availability: The SCIM enterprise extension attributes (including organization) are supported for outbound provisioning across all Microsoft Entra ID license tiers, including Free.

1 answer

Your answer

Shree Varshan G 40 Reputation points

2026-01-09T07:26:54.9366667+00:00

We currently have Azure AD Premium P2 licenses, and we need to understand whether our customers will be able to use SCIM provisioning to sync their company name.

We are planning to map the company name using the Enterprise Organization attribute. However, before proceeding, we need clarification on the following:

If the enterprise attribute is not available for all plans, we need an alternative approach that ensures the companyName is synced consistently across all plans.

Additionally, we would like to confirm whether the permission to edit the “Edit attribute list for customappsso” setting is available in Premium plans, or if it is limited to higher-tier licenses.

This information will help us decide the correct attribute mapping strategy going forward.
VEMULA SRISAI 13,890 Reputation points Microsoft External Staff Moderator

2026-01-09T18:25:39.3533333+00:00

Shree Varshan G Thank you for your follow-up.

Enterprise Attribute Availability: The SCIM enterprise extension attributes (including organization) are supported for outbound provisioning across all Microsoft Entra ID license tiers, including Free. Since you have Premium P2, you can map companyName to urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:organization without any restrictions. Customers on Free tier can also use this mapping.

Alternative Approach: There is no license-based limitation for using enterprise attributes. If you prefer, you can also map companyName to a core SCIM attribute (e.g., displayName) as a fallback, but this is not required for license reasons.

Edit Attribute List for customappsso: The ability to edit attribute mappings (including adding enterprise attributes) is available for all tiers. Premium plans do not restrict this; they only add advanced provisioning features like assignment-based scoping.

References:

Customize attribute mappings for SaaS apps
Shree Varshan G 40 Reputation points

2026-01-10T11:07:46.76+00:00

Microsoft Entra NEVER sends cleared enterprise attributes in PATCH

Not "", not null, not Remove — it simply omits them.

is this true . i need to track the companyName if it is cleared and having values as well i tried after clearing then it is not sended from entra

how this can be fixed any workaround or something im missing
VEMULA SRISAI 13,890 Reputation points Microsoft External Staff Moderator

2026-01-20T17:58:00.3066667+00:00

Shree Varshan G ,Microsoft Entra does not send cleared enterprise attributes in PATCH—cleared values are simply omitted, not sent as null, "", or Remove. This is expected behavior, and the SCIM service treats “missing attribute” as “attribute was cleared.” To track deletes, your SCIM API must interpret omitted fields as removals. There is no Entra-side fix; the workaround is handling this logic in your SCIM endpoint.
Shree Varshan G 40 Reputation points

2026-01-29T09:42:21.0666667+00:00

i found this in google

Enterprise extension attributes—such as department, employeeNumber, and organization (part of the urn:ietf:params:scim:schemas:extension:enterprise:2.0:User schema)—are generally not available in the Microsoft Entra ID Free tier for outbound SCIM provisioning. These extended attributes typically require at least a Premium P1 license.

Key points regarding attribute availability in Entra:

SCIM Provisioning (Outbound): While core user attributes are supported, Enterprise Extension Attributes often require a premium license.

Entra Connect Sync (Hybrid): Basic synchronization of core Active Directory attributes is included in the free tier, but specialized enterprise extension mappings may be restricted.

Alternative: If you are using Entra ID Free for SaaS provisioning, you may be limited to core attributes and cannot use custom enterprise mappings.

the enterprise attributes are available only on premium p1/p2 ? but you are telling

Enterprise Attribute Availability: The SCIM enterprise extension attributes (including organization) are supported for outbound provisioning across all Microsoft Entra ID license tiers, including Free.

Answer 1

The context provided does not specify the licensing requirements for SCIM enterprise extension attributes or their availability across different Microsoft Entra ID licensing tiers. Therefore, I cannot provide detailed answers to your specific questions regarding the licensing for SCIM provisioning and the use of enterprise extension attributes.

For accurate and up-to-date information, I recommend checking the official Microsoft documentation or contacting Microsoft Support directly for clarification on licensing and SCIM attributes availability.

References:

Entra ID - Provisioning & Identity Synchronization

1. Enterprise Extension Attribute Availability

2. Outbound SCIM Provisioning Licensing

3. Default Attribute Mappings

4. Documentation Reference

Follow-Up Questions

References

1 answer

Your answer