chaplic

I live in a world where people are trying to minmise exchange on prem, even if notionally having to have an exchange server on prem for daft MS support requirements So to that end, I would be modifying the AD attributes directly - proxyAddresses and MsExchangeRecipientDisplayType and so on.

Just hiding them from the GAL isn't going to achieve this. Have a look at this, I have a feeling there may be licensing implications Use Microsoft Teams scoped directory search - Microsoft Teams | Microsoft Docs

Im not knowledgeable enough on google consumer to say how it will handle it, but i would say its still the owner of the domains spf and dmarc that is important. Certainly thoroughly test as a quick test may be misleading.

Would that work in scenarios where the originator email domains have strict SPF/ DMARC policies? Gmail may see the emails coming from apple and not the original sender and drop them as spammers

So you're searching for 'fred bloggs' and the account returned '[email protected]' is being shown, and this account is soft deleted and not visible in the AAD portal? If so, agree something is funky. Once I had an issue where we re-enabled the ability for some users to send IMs but some people couldn't despite the usual waiting, reseting cache, patting belly and rubbing head etc. Raised a ticket with MS and the engineer mumbled something about updating the front end, anyhoo 24 later it was sorted.

Are you sure the account in the cloud and the account on prem are one-and-the-same. Get the immutable ID from the cloud object (get-msoluser [email protected] look for immutableID) Convert this to ms-ds-consistencyguid which is (probably) the AD field that links the two powershell - How to return user with specific ms-DS-ConsistencyGuid based on filter query - Stack Overflow

have a search for miisclient.exe

"C:\Program Files\Microsoft Azure AD Sync\UIShell\miisclient.exe" is where it is by default

Does the MIM Admin console on AADC give any clues? find the syncronisation service manager and run as admin. This can sometimes give better error messages

Wait 48 hours. Teams can be really lazy updating stuff, and it's server end not client end so nothing helps.

I think what you're doing is bonkers, but all-the-best. If you are determined to do this, quest-on-demand can migrate contents of mailboxes in the same tenant, doing a compliance centre export is painfully slow (I suspect most tenant to tenant tools would do inter-tenant moves but not tested).

Dont do this! Unless you really, really, really want to start afresh with permissions, content and so on. Just change the existing accounts. I'm assuming you are just projecting your AD accounts to O365, so in AD simply change your userprincipalname to the new desired entry, and add all desired aliases to the proxyAddresses AD field in the format SMTP:[email protected] smtp:[email protected]. Check your client impact as sometimes outlook can be huffy with a new UPN, but worse-case it will want a profile rebuild but may just work.

About 10 minutes after the Microsoft school offering is not free... Son migrated from gmail to Office365. Mailbox move is similar to on prem to exchange but you cannot finish it because MS tries to setup the forwarder which isnt supported in the basic google apps service, so the approach seems to be to set it to sync but not complete. Setting up the permissions for O365 into Google was a bit of a faff too with out-of-date instructions. I Had to write a transport rule to remove spam checking from forwarded as some senders with certain DMARC policies were going into spam in O365, son moaning a bit about UI and asking the question what'll happen to things like hhangouts, which I dunno.

Ive got a free 100 user workspace as I got in v. early. I'm Literally now migrating my sons email from it now to office365, the MS business essentials is cheaper (and in my case actually cost neutral cos I was paying for a onedrive license for him which is the same price) It's not clear what happens to the gmail account post the cutover date, obviously email etc will disappear but I haven't read anything that states if it will just turn into to free account. After my pilot (son) is complete, got the in-laws and parents to migrate. Wish me luck!

To remove the mailboxes, you need to remove the exchange license

your first premise that outlook 2016 does not normally autoconnect is wrong, thus I think you are trying to solve the wrong problem. Make autodiscover work. Create an outlook profile without any mail services, then holding control right click on outlook in bottom right area and select 'test email autoconfiguration'. Enter your email, untick the two guesssmart and click test Errors in the log are not necesarily a problem but needs interpreted... initital thoughts Is there an SCP entry in Active Directory pointing to now nonexistant exchange server? Similarly is there an SRV record in internal DNS? what happens when you call https://school.com/autoidscover/autodiscover.xml in a web browser ? 404 is ok, password prompt is a problem. Do you have any registry keys defined that would disable autodiscover types?

Sending as an alternative address has always been a pain and done via some fudge, e.g. set the desired address as a DL then send as that DL, or a shared mailbox, or setting up a IMAP connection too However MS have introduced a fix - Ive never tried it so interested to see the results Office 365: Now You Can Send Email From Proxy Address (o365reports.com)

mail field in O365 does practically nothing. However, I would reccomend you keep it the same as the primary reply-to address.

Yes, this will change the GAL. The delay is by design and expected

This is my day job (and not a pitch, I'm too busy ;-) You are right to be cautious. Having a single tenant is the right place to be, but getting there is painful. Don't be tempted to start with a new tenant. Consider policies across both tenants and what might be different. The ability to migrate content and quality of that migration is broadly dependant on the age of the tech. So Exchange - nearly perfect, Sharepoint/ Onedrive Good, Teams ok, odd things that plug into teams - terrible, anything that starts power - terrible. Then you've got to think about client side, especially if you have outlook client, teams client and office pro plus licensing. And you've got to figure out how to get identities into the destination tenant. If they current come from AD, you CAN sync the same AD account into two tenants which may help Because of all that a supplier might either be very expensive, or with lots of caveats/ exclusions in what they will deliver for you. So my advise would be to have reasonable description of what your architectures look like, decide what you want transferred, what you don't, how you deal with clients and co-existence. Otherwise you're going to struggle to compare a supplier who'll just press buttons on a cloud based migration tool for you to a suppluer who'll write some bespoke powershell to make user experience better, where needed.

None of that needs to change, that's the beauty of it. I was working for an organisation consolidating it's IT operation and moving mailboxes to the cloud.. one IT manager was not happy and finding reasons why his mailbox couldn't be moved to the cloud. It was moved without his knowledge and he didn't notice for weeks

Ive been working with Exchange on prem since version 4 in the mid 90s and in that time have worked on projects touching hundreds of thousands of mailboxes... I would say go O365 for email. It still requires effort on your part to make it secure and (to a lesser extent) reliable, but its orders of magnitude less complex. The only downside is that it's not 'build and forget'. Your current email system will be pretty much the same as when it was setup. O365 is always changing, not always for the better so you need a plan to keep on top of that.

Yep. Your loginname ([email protected]) doesn't have to bear ANY resemblance to your SMTP address(es) I'm assuming you are syncing your AD accounts to O365, so in AD look at the proxyAddresses field if I have SMTP:[email protected] smtp:[email protected] smtp:[email protected] Then primary reply address will be [email protected] (note the capital SMTP@) whilst they will recieve email addressed to any of those three addresses (assuming registered in tenant obviously)

More of a mailbox, but unquestionably, yes. Coincidentally I was on a confcall today with a GLOBALMEGACORP beating up a supplier who doesn't yet have a working solution for this, and I'd suggest effort that way (or finding a service which is more on-the-ball if your IT budget isnt a telephone number) is more productive than reheating yesterdays tech. But if your organisation has an on prem exchange of some flavour it might be a plan B option.

No. Setup an exchange server, in it's own domain if you want, with domain of your choosing, does not even need to be a public name, let's say nonexistant.local . Setup firewall rules to listen to MS internet range on port 25. Setup a routed connection in O365 for nonexistant.local to point at your exchange server. Setup a mail enabled user object in O365 to receive email to the address you want and forward it to [email protected].