Import Azure Group - Problem with possible Cache
Hi All
After a fresh Delta Sync and the new Group is available in Azure i need to import this Group into Devolutions Server.
But it seems, that Devolutions isnt finding the Group after creation and it creates a type "Custom" Group:
$newRoleData = @{
displayName = $ADGroupName
AuthenticationType = "AzureAD"
}
$NewRole = New-DSRole @newRoleData
The Group is 100% already available online. I can get it via Script and i also see it in Azure Portal.
So i tried to clear the Cache with Invoke-DSResetServerCache @([ServerCacheElement]::All) but it still doesnt find the Group, even not if i directly try it via Webinterface by clearing the Cache at upper right on the O365 Config:
After some time (about 15min?), Devolutions Server finds the "new" Group when i try to manual import.
So it looks for me, that Devolutions Server has still some Cache Informations and doesnt get the Groups directly from Azure.
How can i clear every Azure Cache or possible force in New-DSRole to get the new Group directly from online? Or is there another propper way to clear the Cache via DVSL Module?
Best Regards,
Andreas
Update: I just noticed that when i dont touch the "Custom" Type Group, after the next refresh (in my Case 30minutes), Devolutions automatically changes the Type from Custom to O365. Is there a way to manual trigger this process?
All Comments (2)
Hello,
In fact, because the Office365 in DVLS relies on the cache saved in the database, we must wait for the complete cache refresh before a newly imported Offfice365 group.
When running the Reset cache operation, depending on the number of users and groups and the complexity of the group membership, this will update the information as you mentioned in the update of your post.
A method to monitor how long it takes to completely update the cache is to first enable the Log Debug Information option in Administration - Server Settings - Logging, reset the Office365 cache and then go in Reports - Data Source Logs. You should see Azure Cache start and Azure cache end log entries. The time between those two operations represents the delay of a full cache update. We recommend to disable the Log Debug Information option to lower the debug level back to a normal state.
There is no method to get a new group or user directly from online and can only be processed properly following a full cache refresh. The Invoke-DSResetServerCache cmdlet will start the same process as the one from the web UI Reset Server Cache.
Let us know if you have any further questions regarding the Office365 cache update process.
Best regards,
Érica Poirier
Hi Erica
Thank you very much for your Answer.
I will try to find a Workaround, maybe with a simple 30minutes Timer.
Best Regards,
Andreas