Support articles
Find clear, step-by-step solutions to common WithSecure issues across installation, configuration, updates, and product performance.
Elements Collaboration Protection Exchange-protection was not turned on automatically after adding more licences
Last updated
Issue:
After adding more licenses for Elements Collaboration Protection already existing mailboxes were not automatically protected.
Resolution:
The Elements Collaboration Protection "Automatically protect newly-added mailboxes" setting does not apply to already existing mailboxes in the Elements Collaboration Protection portal. If a mailbox already existed and you increased the amount of available licenses, you will need to enable protection manually on these mailboxes.
When "Automatically protect newly-added mailboxes" is enabled, it means that if a mailbox is added in a protected Azure domain - not visible in Elements Collaboration Protection mailboxes table yet - and then it's discovered, it will be automatically protected at the moment it appears on the Elements Collaboration Protection mailboxes list (if there are licenses available).