{"id":5714,"date":"2023-02-22T08:28:00","date_gmt":"2023-02-22T13:28:00","guid":{"rendered":"https:\/\/www.exchangedefender.com\/blog\/?p=5714"},"modified":"2023-02-21T19:31:03","modified_gmt":"2023-02-22T00:31:03","slug":"new-release-exchangedefender-inbox-m365-hybrid-solution","status":"publish","type":"post","link":"https:\/\/www.exchangedefender.com\/blog\/2023\/02\/new-release-exchangedefender-inbox-m365-hybrid-solution\/","title":{"rendered":"New Release: ExchangeDefender Inbox M365 Hybrid Solution"},"content":{"rendered":"\n
<\/div>\n\n\n\n
\"\"<\/a><\/figure>\n\n\n\n
<\/div>\n\n\n\n

Huge and most demanded feature from our community has finally shipped.<\/p>\n\n\n\n

No more PowerShell. No manual steps. It’s all automated.<\/strong><\/p>\n\n\n\n

When you create a mailbox on ExchangeDefender Inbox the service creates your users M365 account, enables mail forwarding, maps the email addresses correctly, updates routing and signing.<\/p>\n\n\n\n

Anyone can manage Inbox with far fewer IT skills than are needed for the most basic of M365 deployments!<\/p>\n\n\n\n

We’re seeing ExchangeDefender Inbox mailboxes used in companies with high turnover, in companies that are trying to save money (Inbox could save over $300 \/ employee every year!)<\/em>, for mailboxes that get a ton of traffic but are mostly for logging (necessary but rarely ever logged in), temps, external users that need email at that domain but shouldn’t be given an entire M365 license or be exposed to all the data you have on your M365.<\/p>\n\n\n\n

So.. if you’ve been keeping your own Exchange server barely alive just for these types of use case that M365 isn’t ideal for (or worth the $), let’s have a call and save some of your IT budget!<\/p>\n\n\n\n

<\/div>\n\n\n\n

How easy is it?<\/h2>\n\n\n\n

Login to your ExchangeDefender Inbox admin account and choose a tenant to create a user.<\/p>\n\n\n\n

<\/div>\n\n\n\n
\"\"<\/a><\/figure>\n\n\n\n
<\/div>\n\n\n\n

ExchangeDefender Inbox does all the heavy lifting under the hood instantly. Using a combination of Remote PowerShell, Microsoft Graph, and Microsoft’s API for Exchange\/M365 we’re able to create the user, setup forwarding, update address books on both sides and keep everything in sync. The admin doesn’t have to deal with any of that, they just see that it’s done:<\/p>\n\n\n\n

<\/div>\n\n\n\n
\n
\"\"<\/a><\/figure>\n\n\n\n
\"\"<\/a><\/figure>\n<\/figure>\n\n\n\n
<\/div>\n\n\n\n

That’s all it takes to create a mailbox and share the domain with a M365 tenant in hybrid mode. Everyone is on the same domain, everyone has the same format email address, it’s practically the same thing but saves your organization up to 95% every month.<\/p>\n\n\n\n

<\/div>\n\n\n\n
\"\"<\/a><\/figure>\n\n\n\n
<\/div>\n\n\n\n

Everything on the backend is tracked and kept in compliance. Best part – we do not use delete statements anywhere so you never have to worry about ExchangeDefender Inbox creating problems and issues at M365.<\/p>\n\n\n\n

<\/div>\n\n\n\n

Try Inbox today for free! Login to your ExchangeDefender Admin <\/a>account to get started.<\/h2>\n\n\n\n

<\/p>\n","protected":false},"excerpt":{"rendered":"

[…]<\/p>\n","protected":false},"author":50,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[51,32,197],"class_list":["post-5714","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-email","tag-exchangedefender","tag-inbox"],"_links":{"self":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/5714","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\/50"}],"replies":[{"embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/comments?post=5714"}],"version-history":[{"count":2,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/5714\/revisions"}],"predecessor-version":[{"id":5725,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/5714\/revisions\/5725"}],"wp:attachment":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/media?parent=5714"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/categories?post=5714"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/tags?post=5714"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}