Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2021 Release Wave 2Discover the latest updates and new features releasing from October 2021 through March 2022.
2021 release wave 2 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
Present installed AX database using Windows authentication. Client connected to their AD users which I imported in users of AX.
In case, Can I change it to mixed mode.
- Any issue we will face and their workaround
- How can the clients connect from their pc
I would expect it to work, but why would you do that?
Clients would connect in the same way - to AOS. They should never have direct access to database.
Note that AX will always use Windows Authentication.
Setting mixed mode authentication on SQL Server means you are punching a big hole in your customer's security and is not recommended. What is the reason behind doing this?
AX's prerequisite clearly states that an Active Directory domain is required, thus Windows AD authentication is used, no matter what setting you change on your SQL side. Your AX AOS execution account will still need to be a db_owner on the AX databases, and SQL will authenticate user connections via your domain controller. Your regular users would not execute anything on SQL side, but the AOS service account does.
Our client needs to migrate from Physical to Virtual.
Their another 3rd party application running on .Net and SqlServer (Mixed Mode).
So, the company who will be doing the migration is using some tool to move P2V. So they say the procedure differs if Windows authentication with Mixed Mode.
So, before hand I would like to prepare for this scenario if they go for it.
Since our AX installation company used AXadmin user for AX, SSRS installation. Can I change the SSRS with new domain user. What steps need to be done.
If you advice me to place this in seprate thread, then I will do that.
Running SQL Server on a virtual server doesn't require Mixed Mode authentication. These are two independent topics.
It seems that your problem is caused by the fact that you want give a third-party application direct access to Dynamics AX database, which isn't recommend (it would bypass all business logic, all security, would have to deal with implementation details such as table inheritance...). Depending on what you're trying to achieve, you can use web services, entity store and such so on.
You can change domain if you want, although you can continue using the same domain even in virtualized environments.
If the 3rd party application uses a different database from AX, and it requires mixed mode authentication there, the recommendation is that do not move there but create a new SQL instance. You typically want to completely isolate your AX's SQL Server instance from other database/IO/network chit-chat, since an OLTP database has very high demand for resources.
If you are talking about SQL authentication so the 3rd party application could read from the AX database, that can be done, but should not be done due to the above reasons - security. In this case you could expose your data through other interfaces, as Martin mentioned.
If you must provide read access to the 3rd party anyway through Mixed mode, I would set up an AlwaysOn availability group with cloning the AX database to a Readable Secondary replica, where you provide the mixed mode authentication, but not on the Primary instance, this does improve security slightly.
Business Applications communities