{"id":2723,"date":"2019-08-28T13:03:46","date_gmt":"2019-08-28T17:03:46","guid":{"rendered":"http:\/\/www.exchangedefender.com\/blog\/?p=2723"},"modified":"2019-08-28T16:26:11","modified_gmt":"2019-08-28T20:26:11","slug":"managing-exchangedefender-automatic-account-enrollment","status":"publish","type":"post","link":"https:\/\/www.exchangedefender.com\/blog\/2019\/08\/managing-exchangedefender-automatic-account-enrollment\/","title":{"rendered":"Managing ExchangeDefender Automatic Account Enrollment"},"content":{"rendered":"\n

ExchangeDefender recently launched the Automatic Account Provisioning system<\/a> that replaces our old ExchangeDefender XDSync. The new system automatically finds email addresses that are sending out messages and sends a welcome message to provision the account \u2013 the CIO\/MSP get a report with a summary of changes and essentially automates the entire process. <\/p>\n\n\n\n

For compliance purposes we\u2019re making it super easy to keep track of this process and we\u2019re even providing some tools to help manage accidental activation \u2013 for licensing purposes if the email address sends emails out it\u2019s considered a billable user (only inbound aliases\/distribution groups\/contacts are free) <\/em><\/p>\n\n\n\n

As a CIO\/Service Provider<\/h2>\n\n\n\n

If the email address was provisioned through the automation process, you will see an icon A next to the email address in your portal. To manage the accounts you\u2019ll have to hop down to the Domain Administrator. <\/p>\n\n\n\n

\"\"



<\/figcaption><\/figure>\n\n\n\n

As a Domain Administrator <\/h2>\n\n\n\n

Domain Admin control panel at https:\/\/admin.exchangedefender.com<\/a> gives you more granular controls over Automatic Account Provisioning. Under the Accounts section you will find the same A<\/strong> icon next to the accounts that were provisioned automatically. <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

If these accounts were provisioned by mistake and these are not valid users, you can Block them. Blocking an account does two things:<\/strong> it removes the user from the block list so it doesn\u2019t continue to get provisioned after it is deleted and it blocks messages from that user \/ device \/ service from relaying mail. <\/p>\n\n\n\n

To find users that were blocked from automatic activation (in case that address becomes a regular mailbox\/sender in the future) you can click on the Blocked Addresses tab: <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Reporting and activity regarding accounts is still in the same place for both admin levels under the Accounts menu. Accounts that were provisioned through automation will show that they were created by ExchangeDefender Automation, and Blocked Addresses will show the name of the admin that blocked them. <\/p>\n\n\n\n

\"\"

<\/figcaption><\/figure>\n\n\n\n


What about deletions? What about turning this system off entirely? <\/strong><\/h2>\n\n\n\n

We\u2019re working on it \u2013 stay tuned! We\u2019re obviously curious why anyone would want this turned off so if you have a legitimate reason (other than it makes it difficult to cheat on licensing) please let us know. If you have a legitimate use for a service\/device to relay mail out, you can always configure it with a free IoT account in ExchangeDefender.<\/p>\n\n\n\n

We are also currently working on automatic deletions (based on usage patterns) that will be configurable on a per-domain policy. For example, you\u2019ll have the ability to deactivate accounts that have not sent out any email in 3 months. <\/p>\n","protected":false},"excerpt":{"rendered":"

[…]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4,1,8,46],"tags":[159,157,144,158],"class_list":["post-2723","post","type-post","status-publish","format-standard","hentry","category-exchangedefender","category-uncategorized","category-hosted-services","category-product-features","tag-account-enrollment","tag-admin-portal","tag-automated-provisioning","tag-new-accounts"],"_links":{"self":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/2723","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/comments?post=2723"}],"version-history":[{"count":10,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/2723\/revisions"}],"predecessor-version":[{"id":2738,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/2723\/revisions\/2738"}],"wp:attachment":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/media?parent=2723"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/categories?post=2723"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/tags?post=2723"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}