Comments on: Manually Configuring Outlook for Office 365 (Exchange 2013) https://blogs.perficient.com/2014/01/24/manually-configuring-outlook-for-office-365-exchange-2013/ Expert Digital Insights Mon, 20 Mar 2017 15:03:38 +0000 hourly 1 By: Jmtyra https://blogs.perficient.com/2014/01/24/manually-configuring-outlook-for-office-365-exchange-2013/#comment-4163 Mon, 20 Mar 2017 15:03:38 +0000 http://blogs.perficient.com/microsoft/?p=20852#comment-4163 Thank you! This was exactly what I was looking for. 🙂

]]>
By: GrahamP https://blogs.perficient.com/2014/01/24/manually-configuring-outlook-for-office-365-exchange-2013/#comment-4161 Mon, 13 Apr 2015 13:18:42 +0000 http://blogs.perficient.com/microsoft/?p=20852#comment-4161 Thanks you for this, saved my life when we had trouble with amending our DNS and could not get autodiscover working

]]>
By: Rene Strawser https://blogs.perficient.com/2014/01/24/manually-configuring-outlook-for-office-365-exchange-2013/#comment-4160 Wed, 14 Jan 2015 17:26:09 +0000 http://blogs.perficient.com/microsoft/?p=20852#comment-4160 In reply to Ivo.

In order to use the Exchange Online cmdlts, such as Get-Recipient, you will need to create a remote PowerShell session in order to connect to Exchange Online. The following is a snippet from a login script I personally use.
$user = “user@domain.onmicrosoft.com”
# This will pop-up a dialog and request your password
$cred = Get-Credential -Credential $user
#Imports the Local Microsoft Online PowerShell Module Cmdlets and Connect to O365 Online
Import-Module MSOnline
Connect-MsolService -Credential $cred
#Establishes a Remote PowerShell Session to Exchange Online
$msoExchangeURL = “https://ps.outlook.com/powershell/”
$session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri $msoExchangeURL -Credential $cred -Authentication Basic -AllowRedirection
Import-PSSession $session

]]>
By: Ivo https://blogs.perficient.com/2014/01/24/manually-configuring-outlook-for-office-365-exchange-2013/#comment-4159 Tue, 13 Jan 2015 17:32:56 +0000 http://blogs.perficient.com/microsoft/?p=20852#comment-4159 My “Get-Recipient command is not recognized as the name of a cmdlet,… I did copy/past from your article. Went to Step 8 as in http://theucguy.net/connect-office-365-using-powershell/ and Get-Recipient is not part of the msocmdlets. Is an import of some Exchange Server 2013 powershell module required?.I’m missing something…

]]>
By: ZakArt https://blogs.perficient.com/2014/01/24/manually-configuring-outlook-for-office-365-exchange-2013/#comment-4158 Fri, 05 Dec 2014 01:59:27 +0000 http://blogs.perficient.com/microsoft/?p=20852#comment-4158 Thank you very much for posting this, I’ve been looking for this solution for couple of days now

]]>
By: Mike https://blogs.perficient.com/2014/01/24/manually-configuring-outlook-for-office-365-exchange-2013/#comment-4157 Thu, 04 Dec 2014 22:47:32 +0000 http://blogs.perficient.com/microsoft/?p=20852#comment-4157 Thanks very much! This information was perfect, unlike a ton of outdated articles telling you to go to OWA, click the question mark then “About” (which no longer exists) to retrieve the manual server setup. A workaround I used in the past was to set up the external autodiscover record then modify the workstation DNS to discover the 365 server. However, this works perfectly! Thanks again.

]]>