We have business rules active for creating (Office365)accounts.
When a new account is created and activated for Office365 the mailbox is not available straight away because this takes a couple of minutes before the mailbox is created in Office365.
We want to set a couple of extra settings on this new account/mailbox (calendar rights/Folder language and some other settings). How can we tell adaxes to wait till the mailbox is available and then continue running the powershell script to set the specific mailbox settings and all the other steps created in the business rules? I am aware that Adaxes will will queue the Exchange settings available true Adaxes. When running the powershell scripts in the business rules the scripts will fail now because of course the mailbox is not available yet.
When the business rule is completed we are sending the customers the info from this new account. When we configure the above requirements true the scheduled task it is possible that the customers already logged on with the newly created account. For this reason we want to have it implemented in the business rules for creating new accounts.
We do not have a on-premise exchange. So first creating the mailbox on-premise and then move it to Office365 is not a option.
I am curious how others are handeling the creation for Office365 accounts without on-premise Exchange.