Dynamics Community Forum Thread Details

FYI: Outlook Add-In Business Inbox keeps asking for authentication when the Dynamics NAV Win / Web Client is configured with AccessControlService

The CSS support teams did recently work on several support scenario's where a successful authentication in Outlook / Outlook Web Access (when trying to connect to the Outlook Add-In Business Inbox), resulted in a redirection to the same authentication page. In the application event log file, you will see two events show up:

1. Event 232 with description: <ii>A user successfully authenticated against the server.</ii>
2. Event 231 with description: <ii>You do not have access to Dynamics NAV. Verify that EXCH_ID:{GUID} is set up as a valid Dynamics NAV user.</ii>

The reason is that when the Dynamcis NAV Win / Web Client is configured with AccessControlService, the Exchange Identifier does not get stamped in the User Table. A typical Exchange Identifier does look like this:
https://outlook.office365.com/autodiscover/metadata/json/GUID

You can verify this via the User Page in Dynamics NAV Win / Web Client:
- Mapped to Exchange Identifier: not enabled
- (Ribbon): Delete Exchange Identifier Mapping (greyed out)

The product team has been made aware that this is an issue.

CSS defined the following workaround. Via PowerShell create another WebClient instance with authentication type set to NavUserPassword. From the Dynamics NAV Win / Web Client, search for Office Add-In Management, download the manifest file and replace the (all) url(s) for the WebClient with the new one. Deploy the adjusted manifest file.

NOTE: It may be necessary as well to connect to the Exchange Online environment via the Office 365 portal to remove the two Dynamics NAV Add-Ins from Add-In management so that it can take the new one with the adjusted values. It may also be necessary to change the authentication type for the relevant Dynamics NAV Service Tier from AccessControlService to NavUserPassword if it is configured with AccessControlService. NavUserPassword does support both NavUserPassword and AccessControlService.

When you then connect to Outlook, authentication will take place with NavUserPassword and the Outlook Add-In Business Inbox will connect successfully. The authentication request will never be asked again because the mapping is enabled per user.

We do apologize for the inconvenience this may cause to you. We will post updates as soon as the product team figured out how we can also stamp that value in the User table when AccessControlService is being used.

Quick Links

Leaderboard