ezscim

Install the EzSCIM NuGet package, annotate your entity with [ScimProperty] attributes, implement a data repository, and register the SCIM services and controllers in Program.cs. The Skill walks you through each step based on your data stack.

Choose EF Core if your project already uses Entity Framework Core, since EfScimRepositoryBase provides CRUD with no boilerplate. Choose IQueryable for any other data source such as Dapper, Cosmos DB, MongoDB, or custom repositories.

In the Azure Portal, go to Entra ID, Enterprise Applications, your app, then Provisioning. Set the Tenant URL to your /scim endpoint and paste a full JWT with the Bearer prefix as the Secret Token, then click Test Connection.

Yes. The EF Core path supports multiple providers including PostgreSQL, where JSON columns use jsonb instead of nvarchar(max). The IQueryable path works with any data source that can expose an IQueryable, such as Dapper or Cosmos DB.

This happens when QueryUsers or QueryGroups returns IEnumerable instead of IQueryable, or when you call AsQueryable on an in-memory list. Return a true IQueryable from your data source so EzSCIM translates SCIM filters into LINQ executed at the database.

Do not use it for SCIM protocol questions unrelated to EzSCIM, for non-.NET projects, or for Azure AD application registration steps. It only covers integrating the EzSCIM packages into ASP.NET Core hosts.