Last week the 2014 edition of IT/Dev Connections took place at the Aria Resort in Las Vegas and as an Exchange Server MVP I was focusing on the Exchange track.
Yearly Archives: 2014
You can’t use the domain because it’s not an accepted domain
After moving several users successful from Exchange 2013 on-premises to Office 365 at one point the migrated stopped (for some users) with the following error message: “You can’t use the domain because it’s not an accepted domain for your organization”:
Continue reading You can’t use the domain because it’s not an accepted domain
The call to mrsproxy.svc failed. The HTTP request was forbidden
Recently I was doing a project with Exchange 2013 on-premises and Exchange Online in a hybrid configuration (with ADFS etc.). Exchange 2013 was connected to the Internet using a (Juniper) firewall, so no TMG involved. Exchange 2013 was functioning properly.
Continue reading The call to mrsproxy.svc failed. The HTTP request was forbidden
Assign Office 365 license via PowerShell
You can assign a license to a user using the Microsoft Portal, just select the user and in the Action Pane select License. Depending on the licenses you got available you can assign it (in this example an E3 license) and set the user’s location (in this example Netherlands):
Exchange 2013 CU6
On August 26 Microsoft released Exchange 2013 CU6, the sixth Cumulative Update since the new servicing model of Exchange 2013, exactly after 90 days which fits in the quarterly cadence.
Jaap Wesselius 
You must be logged in to post a comment.