-
Bug
-
Resolution: Unresolved
-
High
-
17
-
Minor
-
Issue Summary
User provisioning not updating the account <--> group association in a specific scenario.
Steps to Reproduce
- Create a new user in Azure - make sure it is disabled
- Create a group in Azure and assign this group to the user
- Assign "Atlassian Cloud" app to the group created in step 2
- User provisioning will create the Group in Atlassian but user will not be added to it as Azure will say the object is not active in source
- Enable the user in Azure
- User provisioning will not change anything in Atlassian
- I had to do on demand provisioning for the user - this did create the user in Atlassian but in default group (all members ...) but not in the group to which user is added in Azure!
Expected Results
Account should be added to the group once the user is enabled in Azure
Actual Results
Account is not added to the expected group
Workaround
Re-add the user to the impacted group in Azure (and do an on-demand provisioning)
or
You can use Provisioning on demand to fix this without having to update the user:
In Azure/Entra ID select provision on demand
Select the group the user is missing from in Atlassian Cloud
Select to provision specific users
Select up to 5 impacted users
The provisioning will say the group was skipped due to RedundantImport, but the add member operation will still take place for the missing members.
[ACCESS-1384] User provisioning not updating the group - account association
| Description |
Original:
h3. Issue Summary
User provisioning not updating the account <--> group association in a specific scenario. h3. Steps to Reproduce # Create a new user in Azure - make sure it is disabled # Create a group in Azure and assign this group to the user # Assign "Atlassian Cloud" app to the group created in step 2 # User provisioning will create the Group in Atlassian but user will not be added to it as Azure will say the object is not active in source # Enable the user in Azure # User provisioning will not change anything in Atlassian # I had to do on demand provisioning for the user - this did create the user in Atlassian but in default group (all members ...) but not in the group to which user is added in Azure! h3. Expected Results Account should be added to the group once the user is enabled in Azure h3. Actual Results Account is not added to the expected group h3. Workaround Re-add the user to the impacted group in Azure (and do an on-demand provisioning) |
New:
h3. Issue Summary
User provisioning not updating the account <--> group association in a specific scenario. h3. Steps to Reproduce # Create a new user in Azure - make sure it is disabled # Create a group in Azure and assign this group to the user # Assign "Atlassian Cloud" app to the group created in step 2 # User provisioning will create the Group in Atlassian but user will not be added to it as Azure will say the object is not active in source # Enable the user in Azure # User provisioning will not change anything in Atlassian # I had to do on demand provisioning for the user - this did create the user in Atlassian but in default group (all members ...) but not in the group to which user is added in Azure! h3. Expected Results Account should be added to the group once the user is enabled in Azure h3. Actual Results Account is not added to the expected group h3. Workaround Re-add the user to the impacted group in Azure (and do an on-demand provisioning) or You can use Provisioning on demand to fix this without having to update the user: In Azure/Entra ID select provision on demand Select the group the user is missing from in Atlassian Cloud Select to provision specific users Select up to 5 impacted users The provisioning will say the group was skipped due to RedundantImport, but the add member operation will still take place for the missing members. |
| Support reference count | Original: 16 | New: 17 |
| Support reference count | Original: 15 | New: 16 |
| Workflow | Original: JAC Bug Workflow v3 [ 4244792 ] | New: JAC Bug Workflow v4 [ 4567580 ] |
| Support reference count | Original: 16 | New: 15 |
| Support reference count | Original: 15 | New: 16 |
| Due Date | New: 31/Dec/2026 |
| Development Effort | New: L [ 13033 ] | |
| Was this caused by a recent change? | New: No [ 19032 ] | |
| Status | Original: Needs Triage [ 10030 ] | New: Gathering Impact [ 12072 ] |
| Resolution | Original: Answered [ 9 ] | |
| Status | Original: Closed [ 6 ] | New: Needs Triage [ 10030 ] |
Can't understand how a big tech company like Atlassian can't have direct contacts for things like this. We pay a lot of $ for Atlassian, same for Microsoft and still need to open multiples cases for features that are "standalone" in every other SaaS solution.