How To Deploy Dynamics App For Outlook (On-Premise)
Purpose
The purpose of this post is to set out the direction, steps,scope, and implementation approach for the Dynamics Outlook App configuration item
Audience
This post is intended for Technical Teams/Administrators looking to implement the Dynamics Outlook App for On-premise environments.
Pre-Requisites
Dynamics 365 with IFD Configuration
Dynamics 365 Update 8.2.2.112 (KB4046795)
Minimum ADFS requirement ADFS 3 upwards due to OAuth endpoint
Minimum Exchange 2016 or 2013 with Cumulative Update 14 or later
Office 2016 *Recommended, Office 2013 *Compatible
Supported browsers for Outlook on the web
Dynamics 365 App for Outlook can be used with Outlook on the web on the following browsers:
Internet Explorer 10, Internet Explorer 11, or Microsoft Edge
The following configuration is supported:
Protected Mode is enabled for Internet security zone. To enable Protected Mode: in IE 10 or 11, go to Tools > Internet options > Security tab > Internet.
Protected Mode is enabled for Local intranet security zone. To enable Protected Mode: in IE 10 or 11, go to Tools > Internet options > Security tab > Local Internet.
Add *arup.com URL is in the Local intranet security zone list of trusted websites. In IE 10 or 11, go to Tools > Internet options > Security tab > Local intranet > Sites > Advanced.
Supported Browsers
Google Chrome (latest version) on Windows
Firefox (latest version) on Windows
Apple Safari (version 9 or version 10) on Mac or on OSX
Supported operating systems for Outlook on the desktop
Dynamics 365 App for Outlook is supported on these versions of Outlook for the desktop:
Outlook 2013 and Outlook 2016.
Outlook for Mac.
ADFS Configuration
ADFS Authentication Providers
Forms based authentication is required to be enabled on the intranet zone. Open the ADFS management wizard.
Click Authentication Policies > Primary Authentication > Global Settings > Authentication Methods > Edit.
Click Forms Authentication on the Intranet zone.
Register ClientID URI:
Add-AdfsClient -Name "Dynamics 365 App for Outlook" -ClientId (Unique to your org) -RedirectUri https://your org name/crmmailapp/code_auth.aspx
Removing a Client ID
To remove a client ID you can run one of the two commands below withing PowerShell
1.Remove-AdfsClient -TargetName " Dynamics 365 App for Outlook"
2.Remove-AdfsClient -TargetClientId "Client ID found in dynamics administration”
More up to date information can be seen here:
https://technet.microsoft.com/en-us/library/hh699726.aspx#BKMK_WS2012R2
CRM Server Oath Configuration
Run PowerShell as an Administrator
On the Microsoft Dynamics 365 server, open a Windows PowerShell prompt.
Add the Microsoft Dynamics 365Windows PowerShell snap-in:
PS > Add-PSSnapin Microsoft.Crm.PowerShell
$ClaimsSettings = Get-CrmSetting -SettingType OAuthClaimsSettings
$ClaimsSettings.Enabled = $true
Set-CrmSetting -Setting $ClaimsSettings
Configuring Exchange Mailbox Profile
https://(YOUR EXchange URL/EWS/Exchange.asmx
Exchange Impersonation Configuration
Ensure the service account running the email server profile has impersonation rights on exchange. The below command will enable impersonation rights on exchange, this will need to be done by an Exchange admin:
New-ManagementRoleAssignment –Name:(yourorgname) –Role:ApplicationImpersonation –User:(your service account)
To push the app to users
Go to Settings > Dynamics 365 App for Outlook.
In the Getting Started with Dynamics 365 App for Outlook screen, under Add for Eligible Users (you may have to click Settings if you’re opening this screen for the second or subsequent time), select the Automatically add the app to Outlook check box if you want to have users get the app automatically. If a user has the required privileges and email is synchronized through server-side synchronization, you won’t have to do anything more to push the app to them. For example, if you add the required privileges to a Customer Engagement role, and then assign this role to a new user, they’ll automatically get the app.
Do one of the following:
To push the app to all eligible users, click Add App for All Eligible Users.
To push the app to certain users, select those users in the list, and then click Add App to Outlook.
https://support.microsoft.com/en-gb/help/3189639/-an-impersonation-error-occurred-when-connecting-crm-online-to-exchange
For better performance l would recommend running this with version 8.2.2.329
The purpose of this post is to set out the direction, steps,scope, and implementation approach for the Dynamics Outlook App configuration item
Audience
This post is intended for Technical Teams/Administrators looking to implement the Dynamics Outlook App for On-premise environments.
Pre-Requisites
Dynamics 365 with IFD Configuration
Dynamics 365 Update 8.2.2.112 (KB4046795)
Minimum ADFS requirement ADFS 3 upwards due to OAuth endpoint
Minimum Exchange 2016 or 2013 with Cumulative Update 14 or later
Office 2016 *Recommended, Office 2013 *Compatible
Supported browsers for Outlook on the web
Dynamics 365 App for Outlook can be used with Outlook on the web on the following browsers:
Internet Explorer 10, Internet Explorer 11, or Microsoft Edge
The following configuration is supported:
Protected Mode is enabled for Internet security zone. To enable Protected Mode: in IE 10 or 11, go to Tools > Internet options > Security tab > Internet.
Protected Mode is enabled for Local intranet security zone. To enable Protected Mode: in IE 10 or 11, go to Tools > Internet options > Security tab > Local Internet.
Add *arup.com URL is in the Local intranet security zone list of trusted websites. In IE 10 or 11, go to Tools > Internet options > Security tab > Local intranet > Sites > Advanced.
Supported Browsers
Google Chrome (latest version) on Windows
Firefox (latest version) on Windows
Apple Safari (version 9 or version 10) on Mac or on OSX
Supported operating systems for Outlook on the desktop
Dynamics 365 App for Outlook is supported on these versions of Outlook for the desktop:
Outlook 2013 and Outlook 2016.
Outlook for Mac.
ADFS Configuration
ADFS Authentication Providers
Forms based authentication is required to be enabled on the intranet zone. Open the ADFS management wizard.
Click Authentication Policies > Primary Authentication > Global Settings > Authentication Methods > Edit.
Click Forms Authentication on the Intranet zone.
Register ClientID URI:
Add-AdfsClient -Name "Dynamics 365 App for Outlook" -ClientId (Unique to your org) -RedirectUri https://your org name/crmmailapp/code_auth.aspx
Removing a Client ID
To remove a client ID you can run one of the two commands below withing PowerShell
1.Remove-AdfsClient -TargetName " Dynamics 365 App for Outlook"
2.Remove-AdfsClient -TargetClientId "Client ID found in dynamics administration”
More up to date information can be seen here:
https://technet.microsoft.com/en-us/library/hh699726.aspx#BKMK_WS2012R2
CRM Server Oath Configuration
Run PowerShell as an Administrator
On the Microsoft Dynamics 365 server, open a Windows PowerShell prompt.
Add the Microsoft Dynamics 365Windows PowerShell snap-in:
PS > Add-PSSnapin Microsoft.Crm.PowerShell
$ClaimsSettings = Get-CrmSetting -SettingType OAuthClaimsSettings
$ClaimsSettings.Enabled = $true
Set-CrmSetting -Setting $ClaimsSettings
Configuring Exchange Mailbox Profile
https://(YOUR EXchange URL/EWS/Exchange.asmx
Exchange Impersonation Configuration
Ensure the service account running the email server profile has impersonation rights on exchange. The below command will enable impersonation rights on exchange, this will need to be done by an Exchange admin:
New-ManagementRoleAssignment –Name:(yourorgname) –Role:ApplicationImpersonation –User:(your service account)
To push the app to users
Go to Settings > Dynamics 365 App for Outlook.
In the Getting Started with Dynamics 365 App for Outlook screen, under Add for Eligible Users (you may have to click Settings if you’re opening this screen for the second or subsequent time), select the Automatically add the app to Outlook check box if you want to have users get the app automatically. If a user has the required privileges and email is synchronized through server-side synchronization, you won’t have to do anything more to push the app to them. For example, if you add the required privileges to a Customer Engagement role, and then assign this role to a new user, they’ll automatically get the app.
Do one of the following:
To push the app to all eligible users, click Add App for All Eligible Users.
To push the app to certain users, select those users in the list, and then click Add App to Outlook.
https://support.microsoft.com/en-gb/help/3189639/-an-impersonation-error-occurred-when-connecting-crm-online-to-exchange
For better performance l would recommend running this with version 8.2.2.329
It has been just unfathomably liberal with you to give straightforwardly what precisely numerous people would've promoted for an eBook to wind up making some money for their end, basically given that you could have attempted it in the occasion you needed.
ReplyDeleteBest CRM System