---
title: Known issues and limitations
description: The following are known issues or limitations with the Atlassian Cloud Provisioner.
component: atlassian
page_id: atlassian:atlassian_cloud_provisioner:pf_atlassian_cloud_connector_known_issues_and_limitations
canonical_url: https://docs.pingidentity.com/integrations/atlassian/atlassian_cloud_provisioner/pf_atlassian_cloud_connector_known_issues_and_limitations.html
revdate: July 3, 2024
section_ids:
  known-issues: Known issues
  known-limitations: Known limitations
---

# Known issues and limitations

The following are known issues or limitations with the Atlassian Cloud Provisioner.

## Known issues

There are no known issues.

## Known limitations

* Attributes

  * Due to limitations in PingFederate, user attributes cannot be cleared after they are set.

* Deprovisioning

  * When an LDAP user is deleted in a targeted group distinguished name (DN), the provisioning connector does not propagate the deletion until a new user is added to the group. This limitation is compounded when the **User Create** provisioning option is disabled. For solutions, refer to [SaaS provisioner does not remove the user](https://support.pingidentity.com/s/article/After-deleting-an-AD-user-account-SaaS-provisioner-does-not-remove-the-user-in-the-next-provisioning-cycle-when-Group-DN-is-specified) in the Knowledge Base.

* Provisioning

  * Atlassian only allows users with a verified domain to be created. If a user seems to have synced successfully, but does not appear on the **Managed accounts** page in Atlassian, the user's domain is likely unverified.

  * Due to a limitation in Atlassian, group names cannot be updated.