0 votes

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.

by (100 points)

1 Answer

0 votes
by (257k points)
selected by
Best answer


Adding a delay is not the best solution because creating a mailbox can take a lot of time. The delay is unpredictable. Instead, we recommend using a Scheduled Task and the following procedure:

  1. You can create users in Office 365 with sign in blocked. This will guarantee that your customers cannot log in until you set the necessary properties.
  2. You can create a Scheduled Task that checks whether a mailbox is ready.
  3. When a mailbox is already created, the task sets the necessary properties, unblocks access to Office 365 and sends emails to the customers.

Like support says, use a scheduled task to handle this. What I did was when the account it created, I populated a field in AD with TRUE for the newly created user. Then daily with a scheduled task, i look at all accounts that have TRUE in that field and run the powershell against it.

Related questions

0 votes
1 answer

I need to run a PowerShell on accounts that are 90 days or older. Would that be "if the 'When Created' is greater then or queal to '%datetime,-90d%'" or "if the 'When Created' is less then or queal to '%datetime,-90d%'"

asked Jun 1, 2020 by hgletifer (1.3k points)
0 votes
1 answer

I have an account that I am using as the "run as" account to run PowerShell scripts for several different custom commands. I would like to be able to update the ... a script that updates the credentials used to run a script in an existing custom command?

asked Oct 18, 2021 by KelseaIT (320 points)
0 votes
1 answer

I have a feild called Decommissioned Date and I can not figure out how to run a scheduled task the day after that date. So If an account got decommissioned today I want the task to run tomorrow.

asked Jan 9, 2020 by hgletifer (1.3k points)
0 votes
1 answer

In Web administration I created Action for editing mail enabled group, but default service account doesn have rights to modify exchange. Is it possible to just this one Action pick another account? As it is possible in Custom Command?

asked Nov 21, 2019 by KIT (910 points)
0 votes
1 answer

I have two domains where a sub-set of users are a mirror of each other. When a deprovision is run in the primary domain I would also like it to perform the ... on as well, possibly by calling a separate custom command where I can have different steps.

asked Mar 25, 2016 by Infounlim (470 points)
3,167 questions
2,870 answers
506,075 users