Over the last day or so we have been seeing this pop up under the exchange header in adaxes portal.
cmdlet Get-CASMailbox is not present in the role definition of the current user
For troubleshooting purposes, please, enable tracing of requests sent to Exchange servers, reproduce the issue and send us (email@example.com) the log file. For information on how to enable the tracing, have a look at the following help article: https://www.adaxes.com/help/EnableExchangeRequestLogging.
Our adaxes service account is able to create the mailbox when running our create user business rule, but cannot change any settings like disable OWA. What level of security will it need?
We are using the SeeAlso attribute to store who is responsible for specific accounts. We do not wish to use the Manager field, because the Manager/Direct Report structure is ... to, for example, extende the expiration date of an account. Is that possible?
I would like to change department without a script just yet if possible on multiple accounts. If I cant do this then I will entertain custom script Thanks :)
I am trying to use this script from the script repository: https://www.adaxes.com/script-repository/enable-mfa-with-phone-number-for-a-user-in-microsoft-365-s686.htm I ... if I just didn't install it correctly because Adaxes Powershell doesn't recognize it.
Is there a way to get the name of the user who approved a request and supply that to a step inside of a custom command? For example, HR submits a status change for an employee. ... and pass it as a param in a custom command that is called in one of the steps?