When the AD attribute TargetAddress is synchronised to Office 365, where does it “go”

microsoft-office-365

When I set the TargetAddress in an on-premise environment, I'm able to enable cross domain free/busy lookups in a hybrid cloud environment. In addition, email is forwarded to the TargetAddress, and the envelope/P1 header is rewritten accordingly.

However, I am unable to locate this attribute in any of the Powershell commands for the respective environments (O365, EOP, Exchange, AzureAD).

Where can I find this attribute in the hosted environment, because some aspect of it is present, and affecting email.

Best Answer

The TargetAddress attribute does not get synced, it is on-premises only. The reason for this is that there is no reason to actually sync it.

It is used for the following: You have migrated a user from On-Prem to Office 365 or you have created a remote mailbox user on-premises that has a mailbox in Office 365.

The user is synced to Office 365 and the mailbox lives in Exchange Online. Now, since Exchange is self aware, it will need an object locally to tell it where the user is to be found.

The Target Address says, for this remote user, send mail to this address, the mail then goes through the normal connector mailflow in your hybrid setup and lands in Office 365 where the mail is delivered as normal since it has been sent redirected to the address the user has in Office 365.

Usually for Target Address you would use the mail.onmicrosoft.com domain alias for the user, your on-prem connector points this domain to Office 365.

As soon as the mail lands in Office 365 the mail alias (proxyaddress) will tell Exchange Online where the mailbox is. This is why Office 365 doesn't need to know the Target Address attribute, all is handled by normal mailflow, it is only for On-Prem to know what to do since the mailbox is not in the local Exchange Organisation.

Related Solutions

Uninstall legacy versions of Office when deploying Office 365 Pro Plus

Have you tried using wmic? You could use wildcard operators, and tune them to catch whatever programs you'd like to remove.

For instance, try

wmic product where "name like '%Office%'"

You should catch most of what you're looking to remove. You could tune it further to search specifically for the versions or components of Office you know the machines have installed, but it would be likely fine (after checking a couple cases) to have the 'Office' wildcard blast through; definitely doublecheck though!

So just script up something like this:

wmic product where "name like '%Microsoft Office%'" call uninstall /nointeractive

After you know you have your where clause tuned to catch just what you want. To avoid any issues, you can make it as specific of a query as you want.

Is it possible to see the login history on Office 365

Login history can be searched through Office 365 Security & Compliance Center. In the left pane, click Search & investigation, and then click Audit log search. Please notice that for User activity in Exchange Online (Exchange mailbox audit logging) you need to have mailbox audit logging turned on for each user. Please see Technet article Enable mailbox auditing in Office 365.

Office 365 Admin center Home > Usage > Email activity only shows the last activity time of every user and it doesn't report login failures.

If you have concerns about unauthorized logins, you could improve your security by setting up multi-factor authentication for your users. I recommend this at least for users that have administrative roles.

Best Answer

Related Solutions

Uninstall legacy versions of Office when deploying Office 365 Pro Plus

Is it possible to see the login history on Office 365

Related Topic