Powershell Azuze Exchange 2013 Hybrid Enviroment

I am having issues running Azure Powershell commands from my workstation.
We currently have a hybrid enviroment with some users on premise and others in Office 365 cloud. When ever I try to use the Get-mailbox command to list a user that is in the office 365 cloud I get this response:
The operation couldn't be performed because object <Office 365 User> couldn't be found on '<MyOnsiteDomianController>'.
I have listed the script I use to conect to Azure below:
$Cred = Get-Credential
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell/ -Credential $Cred -Authentication Basic –AllowRedirection
Import-PSSession $Session
Import-Module MSOnline
Connect-MsolService –Credential $Cred

Hello,
Come back and mark the replies as answers if they help and unmark them if they provide no help.
I'm marking the reply as answer as there has been no update for a couple of days.
If you come back to find it doesn't work for you, please reply to us and unmark the answer.
Cara Chen
TechNet Community Support

Similar Messages

Exchange 2013 Hybrid Deployment, on-premise to multiple Office 365 tenants

Hello, we are in the early stages of planning an Exchange 2013 hybrid deployment for a federation of education organisations.
We are planning to use a single on-premise Exchange organisation for staff mailboxes across all member organisations, each member already has it's own Office 365 tenancy for students, which we would like to maintain if possible.
My question is, is it possible (and supported) for an Exchange hybrid deployment with a single on-premise organisation with multiple Office 365 tenants, my understanding is that only a 1:1 deployment is supported, can somebody confirm or clarify this ?
Thanks

I think if you have different AD sites then you can install the DirSync or ADFS for each of them and have one way replication. I 'd aks this question to Office365 Forum and support.
Where Technology Meets Talent

Default frontend receive connector settings exchange 2013 hybrid edition?

Hi,
I am busy setting up a hybrid environment with exchange 2007 , exchange 2013 hybrid edition and office 365.
When installing exchange 2013 it creates a default frontend receive connector, on the security tab anonymous user is also selected.
Should i leave it this way?
At the moment the mx record is pointing to the exchange 2007, in the future i will change the mx record to the exchange cloud.
I can telnet and mail to the exchange 2013 server, but there is no spam protection, do i need the anonymous user if i am not intended to use this for the mx record, i suppose office 365 is going to use this connector.
(ps: still have to run the hybrid configuration wizard, waiting for dns ownership txt record)

Hi Steven,
Just as Ed said, the connector restrict access via IP address. We can also create another ones.
If you worry about the spam, I suggest enabling the Anti-Spam function on MBX server.
More details in the following articles:
Spam Protection
http://technet.microsoft.com/en-us/library/jj218660(v=exchg.150).aspx
Enable Anti-Spam Functionality on Mailbox Servers
http://technet.microsoft.com/en-us/library/bb201691(v=exchg.150).aspx
Hope it is helpful
Thanks
Mavis
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Mavis Huang
TechNet Community Support

Exchange 2013 Hybrid setup & DNS

Greetings! We currently have an Exchange 2010 on prem environment and I have been tasked with getting us into a hybrid state with O365. We already have the tenet portions set up, AD Sync working, etc. My initial thought was to just use
our existing Exchange 2010 servers for the hybrid role, however, upon research it appears that standing up new Exchange 2013 servers specifically as hybrid servers is the suggested route.
My main goal is to do this hybrid deployment with as little impact and change to our environment (and thus user impact) as possible. From what I have read, I will have to change the autodiscover and ews records to point to the new Exchange 2013 servers.
Is it also the case that I will have to redirect OWA to the Exchange 2013 servers? Is there any way to deploy Exchange 2013 hybrid servers in a way that I do not have to change owa, autodiscover, etc?
Thanks in advance!

Hi Joe,
Based on my knowledge, we didn't need to install Exchange 2013 to perform routing.
We can just deploy an Exchange 2010-based Hybrid Deployments.
Please make sure the Exchange 2010 upgrade to SP3.
More details to see:
Hybrid Deployments
https://technet.microsoft.com/en-us/library/gg577584(v=exchg.141).aspx
Thanks
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Mavis Huang
TechNet Community Support

Migration From Exchange 2010 Hybrid to Exchange 2013 Hybrid Deployment

hi,
I have existing Exchange Server 2010 Hybrid Deployment. Planning to migrate to Exchange 2013. However, while schema update, i am facing some errors/warnings as can be seen in attached screenshot.
I have already checked and current functional level in DC is Windows Server 2003. What could be the best steps to troubleshoot the problems and proceed further with Exchange 2013 installation?
Thanks

Hi Muhammad
Can you please give few more information about your environment so that people around here can help you out
I have existing Exchange Server 2010 Hybrid Deployment - Do you have Exchange 2010 and Office 365 in a
hybrid setup now ?
Are you trying to upgrade your on premise Exchange 2010 servers to Exchange 2013 ?
Or Are you trying to migrate your on premise Exchange 2010 to a different forest to Exchange 2013 ?
You can try the below suggestions-
I would better suggest you to follow Microsoft Exchange Server Deployment Assistant - http://technet.microsoft.com/en-us/office/dn756393.aspx
Also i would recommend you to check the prerequisites for hybrid deployment with office 365
http://technet.microsoft.com/en-us/library/hh534377(v=exchg.150).aspx
Cheers !!!
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com Thanks Sathish
(MVP)

Exchange 2013 Hybrid Configuration Wizard OAuth error

Hi,
We are facing following error when we run OAuth configuration after complete the Hybrid Configuration Wizard.
Error:
ScenarioFailureException
Message:
Exchange OAuth authentication couldn‎'t find any accepted domains in your on-premises organization.
Verify you‎'ve configured at least one on-premises accepted domain.
Location:
   at Microsoft.Online.CSE.HRC.Activities.OAuthActivities.GetCertificateActivity.Run‎()‎
   at Microsoft.Online.CSE.HRC.Workflow.Activity.WorkflowBaseActivity.Launch‎()‎
   at Microsoft.Online.CSE.HRC.Workflow.Runtime.WorkflowActivityHelper.Execute‎(ActivityContext context, Boolean launch)‎
   at System.Activities.NativeActivity.InternalExecute‎(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager)‎
   at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody‎(ActivityExecutor executor, BookmarkManager bookmarkManager,
Location resultLocation)‎
Environment:
2x Exchange 2013 CU6 (DAG+one ClientAccess)
Directory Sync Server
No ADFS server since we don't need single sign on
Office 365 E3 Tenant
We have tried manually setup the OAuth configuration according to the below TechNet article but failed when running the ExportAuthCert.ps1
script file. It couldn't match the certificate thumbprint with the location "Cert:\LocalMachine\My"
http://technet.microsoft.com/en-us/library/dn594521%28v=exchg.150%29.aspx
Please help!
Thanks in Advance
Roshan

We have the exact same Issue, tried the exact same setup and NO JOY!! - any resolution yet?
Also found this article:
http://consulting.risualblogs.com/blog/2014/09/10/exchange-2013-cu6-hybrid-users-with-o365-unable-to-query-freebusy-for-on-premises-users/comment-page-1/#comment-5192
..... but did not fix the free/busy
Best Regards,
Francois

Exchange 2013 Hybrid and Rightfax

We are in the process of planning our migration to Office 365, and one of the things we currently use in our Exchange 2010 on prem solution is Rightfax for direct faxing inbound/outbound. The plan is to roll out exchange 2013 in hybrid mode, and I
am wondering what i need to do so that faxing continues to work?
Since we will be running a hybrid, is it as simple as installing the rightfax service on the exchange server, or do I need to plan for some kind of cloud access, similar to how they borked up exchange UM integration (requires a session border controller,
rather than routing through exchange on premises box).

Hi,
According to the description, following is my understanding:
1. You want to migrate to Office 365 from Exchange server 2010.
2. Exchange server 2010 host the Rightfax, now.
3. You want to install a new Exchange server 2013 on-premise. Let the Exchange server 2013 on-premise host the Rightfax.
4. Exchange server 2013 on-premise and Office 365 Hybrid Deployment.
Please correct me if there is any misunderstanding.
If all of above is right, I find some resource relate on Hybrid Deployment with Exchange 2013 on-premises and Office 365.
Exchange Server 2013 Hybrid Deployments
http://technet.microsoft.com/en-us/library/jj200581(v=exchg.150).aspx
Note: If you want to move mailboxes from your on-premises organization to the Exchange Online organization, and those mailboxes are configured for UM, you should configure UM in your hybrid deployment prior to moving those mailboxes.
If you move mailboxes before you configure UM in your hybrid deployment, those mailboxes will no longer have access to UM functionality.
About the Rightfax, I find this from Microsoft resource:
OpenText RightFax version 10
http://pinpoint.microsoft.com/en-us/applications/opentext-rightfax-version-10-12884918124
However it works with
Hyper-V, Microsoft Exchange Server 2010, Microsoft Office 365, Microsoft SharePoint Server 2010, Windows Server 2008 R2.
I'm not quite familiar with it. We can also contact to Rightfax Support to double confirm this.
Thanks
Mavis
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Mavis Huang
TechNet Community Support

Exchange 2013 Hybrid Deployment issues.

Hello.
i have an issue when configuring Exchange hybrid deployment in my environment.
when i complete the Exchange hybrid wizard and OAuth is finished our exchange environment will not receive emails from the "internet" as in senders outside the company.
mail will can be sent out and will flow between internal users.
when i check the message trace on 365 the emails were failing with the following error.
Users were also getting a bounce back saying
Diagnostic-Code: smtp;550 5.4.1 [[email protected]]: Recipient address rejected: Access denied
i wondered if it had anything to do with the MX record on our public DNS, i changed this to the one recommended by O365 domain DNS assistant, but this made no odds,
it looks like it could be a receive connector issue however i am new to exchange so i am still learning.
the only way to fix the issue was to run Remove-Hybridconfiguration on the Exchange 2013 server, when this finished and few moments had passed mail began being received from the internal again.
Any Suggestions on what could be caused
many thanks

Hello.
i have an issue when configuring Exchange hybrid deployment in my environment.
when i complete the Exchange hybrid wizard and OAuth is finished our exchange environment will not receive emails from the "internet" as in senders outside the company.
mail will can be sent out and will flow between internal users.
when i check the message trace on 365 the emails were failing with the following error.
Users were also getting a bounce back saying
Diagnostic-Code: smtp;550 5.4.1 [[email protected]]: Recipient address rejected: Access denied
i wondered if it had anything to do with the MX record on our public DNS, i changed this to the one recommended by O365 domain DNS assistant, but this made no odds,
it looks like it could be a receive connector issue however i am new to exchange so i am still learning.
the only way to fix the issue was to run Remove-Hybridconfiguration on the Exchange 2013 server, when this finished and few moments had passed mail began being received from the internal again.
Any Suggestions on what could be caused
many thanks
Make sure the accepted SMTP domains in the Office 365 EAC are set to Internal Relay rather then Authoritative.
Twitter!:
Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Exchange 2013 Hybrid with O365 - migrated user causes admin restart prompt for multiple other users

Greetings! We are in the process of doing some testing and migration in a hybrid deployment with Office365 and Exchange on premise.
I just completed a migration for an on-premise user. We have, so far, migrated 3 users in the IT department as initial testing. The first two migrations were very cut and dry. The third migration; as soon as I finalized the batch, multiple
people on our team received messages about having to restart Outlook. These were users that had not been migrated and were not part of any migration batch, but were members of the same department. I am trying to understand, under what circumstance
could a migration of a user cause other users who are still on premise to receive the "admin made changes" prompt in Outlook.
Thanks in advance.

Hi Joe,
Could you share the migration batch? Note, please hide if there are any sensitive information like domain name and server name.
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Exchange 2013 hybrid configuration

Hi,
I'm using Symantec Bridge mail with Exchange 2010.
And I've planned for Hybrid configuration with Exchange 2010, for this I've created a trail O365 account.
I'm planing to verify the TXT record for my domain, will this affect my present mail flow ?
Sathish

No, mail flow is controlled by the MX record. Creating a TXT record for the purposes of verifying the domain for Hybrid will not affect anything.

Exchange 2013 Office 365 Hybrid Cloud On-Premise Outlook Connection Problem

Hi Everyone,
We are required to migrate FROM the cloud TO an on-premise Exchange 2013 server. We set up a trial of Office365 and linked our test domain to that account. The test domain mimics our current domain, but ends in .net instead of .org.
We set up a test Exchange 2013 server with a few database servers. Internally, we can connect without issue (Outlook). We mapped our test CAS to face the Internet, and can access what we need without issue. We also set up the Hybrid
configuration on both the Exchange 2013 and Office365 servers. We have validated that DirSync works, and migration can occur up to the cloud and back down to the on-premise server.
Now, here is the issue:
We have our DNS records still pointing to Office365, so when we add an Office365 mailbox to Outlook (internal to the network or outside the network) we see absolutely no issues. We migrated a mailbox today to our on-premise server, but upon doing so,
can no longer connect to, or add, that mailbox to Outlook. When we put this integration in to effect for production, we want to be able to migrate mailboxes on-premise from the cloud, and we want to make sure users can still access their mailboxes. This
also goes for distribution groups, conference rooms, etc.
I see that most suggestions say to change your DNS record to point to the on-premise Exchange server, which is great, but after doing so Office365 accounts experience the same issue as above. We NEED to make sure that when we batch migrate, the users
DO NOT lose connectivity to their accounts. We need both Office365 accounts and Exchange on-premise accounts are accessible internally and externally. As an extra tid-bit, we HAVE configured Outlook Anywhere on Exchange 2013, but see no difference.
Any thoughts on this? Office365 and Exchange 2013 see eachother and recognize that the hybrid environment is set up good, but it appears we are missing some configurations. Currently, we have a CNAME record points our autodiscover to autodiscover.outlook.com.
Any help would be MUCH appreciated. Thanks!
Dan

Hi,
Here is an article on Move mailboxes between on-premises and Exchange Online organizations in 2013 hybrid deployments, for your reference:
http://technet.microsoft.com/en-us/library/jj906432(v=exchg.150).aspx
I want to make sure OWA works well with the moved mailbox.
To use CNAME based autodiscover method, we need to have all domain names present in a SAN certificate.
With Exchange 2013 CU1, we now have the option of adding multiple SMTP domains to Exchange Federation/Hybrid configuration and we can specify which of these domains should act the "autodiscover" domain.
To configure an SMTP domain as the autodiscover domain, you can run following command:
Set-HybridConfiguration -Domains "domain1.com, domain2.com, domain3.com", "autod:domain.com"
More details, please refer following blogs:
http://www.msexchange.org/articles-tutorials/office-365/exchange-online/configuring-exchange-2013-hybrid-deployment-and-migrating-office-365-exchange-online-part11.html
http://www.msexchange.org/articles-tutorials/office-365/exchange-online/configuring-exchange-2013-hybrid-deployment-and-migrating-office-365-exchange-online-part12.html
Disclaimer:
Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure
that you completely understand the risk before retrieving any suggestions from the above links.
Thanks
Mavis Huang
TechNet Community Support

Hybrid deployement of exchange 2013

Hi,
We have a small requirement :
Presently our 0365 users are accessing the owa through a URL and we want the onprem users also to access with the same URL ,
how can I achieve this ? do I need to configure ADFS ?
Thanks

Hi,
Thanks for Ed's suggestion.
Also providing a useful blog on Configuring an Exchange 2013 Hybrid Deployment and Migrating to Office 365 (Exchange Online):
http://www.msexchange.org/articles-tutorials/office-365/exchange-online/configuring-exchange-2013-hybrid-deployment-and-migrating-office-365-exchange-online-part15.html
Disclaimer:
Microsoft is providing this information as a convenience to you.The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure
that you completely understand the risk before retrieving any suggestions from the above link.
Hope it is helpful
Thanks
Mavis
Mavis Huang
TechNet Community Support

Hybrid Exchange 2013 rather then 2010

Hi.
On a lots of blogs i find that the costumer will have advantages to upgrade the hybrid server (On-Prem) from Exchange 2010 to 2013. Witch advantages is there? I can see that the
EAC and the Portal merges better, but is it any other god reasons?
Rinken

Hi,
Both on-premises Exchange 2013 and Office 365 have their own pros and cons. You can refer to the following article for more details about comparing Office 365 pros and cons with Exchange 2013.
http://searchexchange.techtarget.com/tip/Comparing-Office-365-pros-and-cons-with-Exchange-2013-hybrid-setups
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software
or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
More information about Exchange Server 2013 Hybrid Deployments:
http://technet.microsoft.com/en-GB/library/jj200581(v=exchg.150).aspx
Hope this is helpful to you.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Belinda Ma
TechNet Community Support

Howto deploy a temporary exchange 2013 server for migration between two Office 365 accounts?

Objective:
We plan to migrate our office 365 from our current tennant (E3) to a new tennant (M) to drastically cut our annual costs for the same services, while retaining the mail and group memberships of all our users. This will involve installing an exchange server
to download and upload mail from the old tennant to the new tennant.
Background:
We are a longtime O365 customer, and have been a customer since before the "Midsize business" plans existed. There is no "cookie cutter" migration path from E3 to M. Microsoft currently recommends deploying an MS exchange server and off-boarding
the mailboxes from your E3 subscription and then On-boarding them to a new account under the M plan. As ridiculous as this is, this is indeed the path our company has decided to go. It isn't cool/fair that we're being shackled to the E plans (that are
vastly more expensive) when we're a small/midsize business that has been a longtime customer of O365, while new customers of equal size to us can expect to save over $4000 annually. The services (when compared) offered are nearly identical.
After calling MS support several times for guidance for this issue, I am advised that we should contact a 'partner' and ask for their support in doing this migration. We did as requested and were provided a quote to the tune of approximately $15,000 to do this
migration for us. Obviously this is unacceptable, and thus our business has decided to rely on my abilities to get it done. Again, involving an MS partner is not an option.
Environment:
1 MS AD domain:
- Original FQDN was @contoso.ca of this domain and UPNs were [email protected]
- UPN has been changed to [email protected] to allow for ADFS
- ADFS has been deployed and SSO works for all users with UPN [email protected]
- An "On-Prem exchange server" does not yet exist
1 O365 Account where main tennant FQDN is @corp.com
- There are 5 registered domains
-contoso.ca
-corp.com
- contoso.legacy.ca
-deprecated/will be deleted
-deprecated/will be deleted
- There are 40 E3 licenses, all using a @corp.com UPN
- There are 5 E1 licenses (we acknowledge that these will be upgraded to an M following the migration) that use the UPN contoso.legacy.ca
- No accounts currently use contoso.ca for email
- O365 was upgraded to 'the latest version' sometime in summer 2013.
Migration Plan (High Level):
Setup a local windows server (trial license)
Deploy an exchange 2013 server (trial license) on the aforementioned windows server http://technet.microsoft.com/en-us/evalcenter/hh973395.aspx
  Prepare and deploy Dirsync Deployment
of Dirsync
Add exchange to office 365 and begin replicating the mailboxes from the cloud to the exchange server. Wait for synchronization to complete.
More information: http://technet.microsoft.com/en-us/library/hh534377(v=exchg.150).aspx
http://help.outlook.com/en-us/140/ff633682.aspx
Evaluate total time it took to sync data.
Time it takes to download data to exchange should be relatively similar to time it takes to restore mail to the new service.
Open a new office365 account under the M plan.
  Plan a 1 hour mail & contoso.ca domain login outage
temporarily change all user UPN's to match the new tennant
perform a dirsync to the new tennant
disable dirsync after all accounts have been auto-created/provisioned
re-establish UPN + mail access.
Plan a date and time for the cut over.
remove the exchange hybrid server from the old tennant.
Point MX records directly to the exchange server.
Cut office 365 service.
  After the 30 minutes ~ 1 hour 'mandatory' wait time imposed by MS to 'register' the domain with O365, add @corp.com to
the new tennant
fix all user UPN's in the cloud to match their real UPN's.
This can be done with powershell.
attach exchange hybrid server to new tennant
Point MX records to the new tennant
Migrate all data from the local exchange server to the cloud under the new plan.
Current progress (Lab):
I have created a sandbox (Lab with no internet access or connectivity to production) environment in VMware and cloned the following servers to it:
1x Domain Controller (DC) running windows server 2012 (named DC02)
1x DC running windows server 2008 R2 (named DC01)
1x windows server 2012 R2 - prepped with all the pre-requisites to install exchange 2013. (named EXC01)
Where I am stuck / Problem:
I have installed exchange on the server EXC01 in the lab environment using my account. I am a domain administrator in the contoso.ca domain, but my UPN is [email protected].
After the installation of exchange, I notice that my email address in Active Directory changed from @corp.com to @contoso.ca. By default, I do not see @corp.com to be an available email address to select as my email address, and changing it in AD does not resolve
the problem.
In the exchange portal, I found "Mail flow ---> Accepted Domains", and believe I should add @corp.com to the accepted domain list. Questions:
1) Must I add corp.com and the other domains that exist in office 365 to the local exchange before I go through with the hybrid wizard?
2) If I must add them to exchange, I am provided with three choices:
- Authoritative Domain
- Internal Relay Domain
- External Relay Domain
Given that the domain is currently in office365 and is authoritative there, which of these applies?
3) Most documentation I have found has been about a one way migration from on-prem to the cloud. I have had a hard time finding a step by step guide for cloud to local (new server) and then back to cloud. Does anyone here have any good documentation for this
process? Would love it if it took into consideration multiple UPN/email addresses.

Hi,
Here are my answers you can refer to:
1. Yes, we should select the primary SMTP domain for our organization and any other accepted domains that will be used in the hybrid deployment:
http://technet.microsoft.com/en-us/library/jj200787(v=exchg.150).aspx
2. It depends on the usage of the specific accepted domain. And Exchange version has no influence.
To determine it, you can firstly check the function of the three types in the following article:
http://technet.microsoft.com/en-us/library/bb124423(v=exchg.150).aspx
3. Here are some reference about the migration from on-premise Exchange server to Office 365:
http://www.msexchange.org/articles-tutorials/office-365/exchange-online/configuring-exchange-2013-hybrid-deployment-migrating-office-365-exchange-online-part1.html
Additionally, since the issue is related to Exchange online, I recommend you ask for help on our Exchange online forum to get more professional help:
http://social.technet.microsoft.com/Forums/msonline/en-US/home?forum=onlineservicesexchange
If you have any question, please feel free to let me know.
thanks,
Angela Shi
TechNet Community Support

Is Windows Azure officially supported for Exchange 2013?

Though Exchange 2013 can be installed on Windows Azure, however can somebody help me in knowing that if its officially supported with it OR can live environment of Exchange be setup on Windows Azure?

Hinte is correct.
You can set up a Exchange 2013 lab in Azure. You may have seen that Henrik Walther has done just that:
http://www.msexchange.org/articles-tutorials/office-365/exchange-online/deploying-exchange-2013-hybrid-lab-environment-windows-azure-part1.html
But this is just for practice / training.
Besides lack of support, cost of sufficient resources to run E2K13 correctly would be greater than simply using O365 / Exchange Online.
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Powershell Azuze Exchange 2013 Hybrid Enviroment

Similar Messages

Maybe you are looking for