Provisioning

I would like to be able to exclude certain AD accounts from getting an exchange mailbox. So it should become an entitlement of the AD Target Connector, just like account access for instance. Now I have to create 2 AD target systems to achieve this.

With the button we can check if the connection is successfully from a agent to the Exchangeserver.

Starting from Exchange 2019 Cumulative Update 12, there's an option to install only the Exchange Management Tools to create/update/remove recipients in an Hybrid environment. This negates the requirement for running a resource-hungry On-Premises Exchange Management Server. I expect more and more organisations will want to start using this. For HelloID Provisioning this means that Remote PowerShell can't be used anymore to create/update/delete Remote Mailboxes for mailboxes in Exchange Online, since there's no full Exchange Server anymore in this scenario. HelloID can support this configuration by requiring the Exchange 2019 Management Tools to be installed on the system where the HelloID Provisioning Agent is running on. The provisioning process should then use the locally installed Management Tools to perform the Exchange Recipient tasks. Please see https://docs.microsoft.com/en-us/exchange/manage-hybrid-exchange-recipients-with-management-tools

Option to make user member of shared mailboxes

As an HelloID Administrator, I would like to create and disable an Exchange mailbox when my AD account is created. This because the Exchange mailbox is closely integrated with AD account and the AD account should always exist before creating an Exchange mailbox. With this, we can easily create a mailbox and manage the settings in the AD connector. The Exchange is optional because not every customer has an Exchange anymore. Could be that they are using a hybrid with AD -> AD connect -> AzureAD (Office365). To support hybrid you need the AD connector and the AzureAD connector. Where the AD connector is used to create local AD accounts and AzureAD with correlation to connect the account to the person and provisioning the Office365 license. In the future, we can add out of office message and options like that inside the Exchange mailbox options. Optional to use Exchange inside AD connector Allow connection with Exchange when adding the AD system (optional). Support complex mapping on proxy addresses table in AD (array of email addresses) Add a new tab with Exchange mailbox settings Add option on to create a mailbox on AD create Create\enable mailbox on AD account creation Add option to enable hide from address book flow on create make it hidden from the address book on enable make it visible from the address book on disable make it hidden from the address book

When the user for exchange online integration is unauthorized because the service account is deleted for example. This error isn’t showed at the Entitlements History tab > Show support information. In the google cloud log this error can be found. I would like to see the google cloud log “Unauthorized (401), message: Authentication for Exchange Online failed” or any other additional information added/shown to the show support information popup.

Consider using the newer cmdlets that allow for mfa login https://docs.microsoft.com/en-us/powershell/exchange/exchange-online/connect-to-exchange-online-powershell/mfa-connect-to-exchange-online-powershell?view=exchange-ps https://docs.microsoft.com/en-us/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2?view=exchange-ps

Please fix the annoying bug with the following constellation: Error message: Failed to update hidden from address list property in Exchange Online If you activate the Exchange Online integration inside HelloID and provision license groups for the M365 licenses (like e.g. E1, E3, E5) with security groups, you will run into a problem inside the offboarding of a user. The problem here is that HelloID will revoke the security group for the license. M365 will unassigne the licenses inside M365. with this action, HelloID can't process the action "Failed to update hidden from address list property in Exchange Online". The workarround at the moment is to assign the license manual inside M365 and rerun the entitlements to offboard the user correctly.

We use MFA on all our systems so we cant use any of the premate scripts because they dont work with mfa.... We would like the option/new version of tasks to user the App authentication module. https://docs.microsoft.com/en-us/powershell/exchange/app-only-auth-powershell-v2?view=exchange-ps It is only a change to the connect line. We would like this change in Onedrive, Azure AD, Office 365

We have implemented HelloID to secure our Microsoft 365 / Azure Cloud environment. For various IT services it is necessary for Active Directory service accounts to access e.g. the Microsoft EWS interface or Exchange Online mailboxes without HelloID requests. Since in these cases no "real" user can confirm the HelloID requests, we currently cannot provide some necessary IT services. Since we have several e-mail domains, we can offer to move these service accounts into a separate domain. We have already discussed these requirements with your colleague in Germany, Mr. Kellers.