Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 264 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 384 SQL Performance
- 33 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
Outlook Integration - Prefers SaaS to OnPrem
eYe
Member Posts: 168
Hi,
Our config is completed according to Microsoft documentation.
However, we have a SaaS Sandbox environment but using OnPrem for Production.
We downloaded the outlook add-in files from the OnPrem installation and added them to Outlook.
If you open it up, you can see everything is pointing to the OnPrem instance.
However, when you open up the app inside Outlook, it tries to connect to the SaaS instance.
This has been verified by a user that doesn't have a login into the SaaS environment, it tells them the username and password is incorrect.
For a user with a SaaS login, it opens, but then accesses the SaaS data.
It feels like there has to be a AAD config that might be wrong/missing.
The redirects on the Azure app registration is pointing correctly to the OnPrem instance.
Kind Regards,
Ewald
Our config is completed according to Microsoft documentation.
However, we have a SaaS Sandbox environment but using OnPrem for Production.
We downloaded the outlook add-in files from the OnPrem installation and added them to Outlook.
If you open it up, you can see everything is pointing to the OnPrem instance.
However, when you open up the app inside Outlook, it tries to connect to the SaaS instance.
This has been verified by a user that doesn't have a login into the SaaS environment, it tells them the username and password is incorrect.
For a user with a SaaS login, it opens, but then accesses the SaaS data.
It feels like there has to be a AAD config that might be wrong/missing.
The redirects on the Azure app registration is pointing correctly to the OnPrem instance.
Kind Regards,
Ewald
Kind Regards,
Ewald Venter
Ewald Venter
0