Microsoft Dynamics AX Reviews

In 2012, I analyzed the market and found that Microsoft Dynamics provides services all over the world. We chose the product based on that criteria. It's been amazing. 

We're using the solution for financial modules, specifically focusing on consolidation, financial configuration, management reporting for warehousing, sales, and some customizations related to the sales module. As an investment company, we configured the sales module to function like stock sales, which allowed us to sell stocks and manage sales processes accordingly.

The solution has automated manual daily operations across multiple departments, especially in financial operations and the business cycle. The business has achieved its module. 

It has streamlined sales, warehouse management, and inventory processes and facilitated easy acquisitions. I’m presently analyzing the product for subsidiaries’ usage, not for my holding company.

Most of the features of Microsoft Dynamics AX are good. The overall structure and functions of the solution are great.

The product needs better admin control, and there is room for improvement in flexibility, reporting, and dashboards. Artificial intelligence should be incorporated. I also have concerns regarding partners, specifically in the implementation and deployment of Microsoft Dynamics. The partner we engaged with within Egypt lacked awareness of many features during the configuration and implementation.

It was strange to find the partner unaware of the function and service that Microsoft granted him to develop and deploy for their customers. This was a big issue. Microsoft needs to establish specific criteria for selecting representatives. It's not just about sending representatives but also about how you add value to the customer. I'm seeking not only to proceed with the Microsoft Dynamics Series but also to engage with a representative who can address and represent my business needs.

I have been using this solution for the past ten years.

The solution is stable. However, the stability is average compared to SAP and Oracle.

The product is scalable. We have 16 users for the solution.

Only two individuals are needed to cover for technical support.

The initial setup is straightforward. I have no issue regarding the system with my team. The deployment is okay. However, it is not about deployment. It's about configuration. Deployment is a group of steps. The main thing is to configure. Moreover, the product is currently deployed on-premises, but I want to move it to the cloud.

Right now we are not paying for licenses.

I’m working with Odoo.

Overall, I rate the solution a seven out of ten.

The product helps us to operate in various sectors apart from producing associated calls. They cover areas like warehouse management, finance, and more. We usually have medium to large enterprises as customers.

Supply Chain Management is an excellent feature. Finance also performs well. There's an element of project management present, which I think makes it a good overall product.

There is room for improvement when handling various currencies within the current Microsoft Dynamics AX system. The ability to manage different currencies like USD or Euro while maintaining separate books of accounts requires improvement without the need for customization.

I am using Microsoft Dynamics AX for three years.

The stability has been satisfactory and there haven't been any other areas of concern.

It is scalable. 

The overall support is good, however, I haven’t processed it myself. 

Positive

I initially worked with SAP solutions. The difference relies on the user's needs, as they are highly competitive and operate across various industries. Thus, they are equally proficient.

The setup is straightforward but, there have been certain problems. However, with Microsoft, there are ample resources available on the platform to address these issues effectively. This is definitely a positive aspect.

The solution is deployed on the cloud and requires two to three people for maintenance. 

In relation to the cloud, it might be expensive for a longer duration. However, it's essential to consider the demands of enterprise users. While it's cost-effective in the short run, it becomes relatively costly in the long run.

 I recommend the solution and I would rate it a seven out of ten overall.

We use Microsoft Dynamics AX to fulfill our requirements. From production and the supply chain to finish, with everything, it meets our requirements. 

Before we had it deployed on-prem, but now we are using it on the cloud. 

The most valuable feature of Microsoft Dynamics AX is that it fulfills our requirements. We haven't had any issues with performance. 

Microsoft Dynamics AX could be improved by having more features available. We are going to 365 now, to use all the modules, because we found that there weren't many new things we were able to develop with AX. There were a lot of things that weren't available, so we are moving and integrating other things. 

The customization of upgrades should also be faster. We would also like to see more security features. 

We have been using this solution for 13 years. 

This solution is stable and the performance is okay. 

This solution is scalable, and we haven't had any issues. 

There are 100 end users of this solution in our organization. 

Microsoft's technical support is good. 

The initial setup was straightforward, but data customization took time to upgrade to 365. If it's just an upgrade, then it's easy, but the customization upgrade took time. We did it ourselves, but we obtained some outside help. 

We implemented this solution through an in-house team of two admins, but had some outside help. 

We pay for licensing yearly to use Microsoft Dynamics AX. 

I rate Microsoft Dynamics AX an eight out of ten. 

Whether or not someone should implement this solution depends on their user requirements. For us, it's for 100 people, so it's good, but I'm not sure if it would be good for more than 100 people. For a medium-sized business, it's good. 

The use case includes pretty much everything from finance to warehouse to production.

The production is a valuable feature. 

The general speed of the solution needs improvement.

I have experience using Microsoft Dynamics AX for a year. 

The solution is highly stable. I rate the nine out of ten. 

Twenty five users are using the solution. 

The initial setup is complicated. The deployment takes eight months. 

Overall, I rate the solution an eight out of ten. 

We belong to a manufacturing automobile company, and we are using this application for:

• end-to-end ERP 
• Enterprise resource planning application right from our stores
• Production planning to logistics
• Finance
• Quality.

The solution has improved our organization because, at that point in time, our whole isolated function came into a single system. It was the first step to digitizing the machine process.

The most valuable feature I've found is the UI functionality, user interface functionality. It's great. 

The biggest improvement needed with the solution is security control or rights control to internal users. There is much improvement needed in that product line. Gradual level controls were missing, or if we are allowed some controls, then it will automatically go to different ones. We cannot give proper controls or user rights to internal user sections.

There is also slowness in database backup.

We started our journey with Microsoft Dynamics AX in 2009 and have been using the solution since early 2011.

In terms of functionality, it's a stable product, but frankly speaking, looking at the market footprint in the Indian market, there are two fewer customers in India for Microsoft ERP. If there is some kind of new functionality required, then there is very high dependability on specific partners. The technicality exporting that level of that product from that partner community is limited, compared to other established products like SAP or other solutions.

The scalability is similar to stability. It's generally scalable.

We've had up to 200 users but we currently have around 100 with no plan to increase usage.

We have not taken much support from the Microsoft tech team directly. We generally deal with that from our partner community.

Before we switched to Microsoft Dynamics, we were using Fox ERP Solutions. It was a solution
with limited functionality and isolated functions. There is no scalability at all from the FoxPro application. At that time, we had five locations, and each location we had to keep altogether with a different kind of setup, different servers, different team to manage that, but we want an integrated feature, so we move from the Fox ERP solution to Microsoft.

The initial setup is not so simple or not so complex as well. It's a three-tier architecture. We have the application tier, database tier, and presentation level. It's a moderate setup at first. The full deployment took around six months.

We implemented with help from an external team, Godrej Infotech. They implemented that solution for us in our organization.

It depends on the scale of the organization or the functionality of the product, but to maintain this product in-house, will require around four or five people.

We have been using the product for the last 10 years, so we have some return on our investment.

When we first implemented the solution, Microsoft licensing was cames with the concurrent use licensing. Nowadays, even if we procure the license, the additional cost of the operating system, the additional cost of database licenses, the additional cost of Visual Studio, and the additional cost for Microsoft Office and that all. If we need to access that from remote locations, multiple branches, then we need to procure remote desktop services licenses. So apart from licenses of Microsoft ERP, there are multiple licenses, supporting licenses we need to procure. That is the disadvantage of the solution. The ownership cost or, rather, whatever the initial investment cost goes up due to this hidden cost. Initially, that is not considered in many things.

Before we switched to Microsoft Dynamics, we also consider Baan, Oracle, and SAP at that point in time.

I would rate the solution a six out of ten.

It will serve all basic purposes but from an analytics perspective, there will be some limitations. You will not get ready-made things from the solution. You need to develop or you need to integrate with multiple products to see that kind of reporting from it.

Microsoft Dynamics is a tool that we use for both online requirements and customer changes, as well as for development purposes. The main advantage of this tool is that it allows us to take change requests online, which speeds up the implementation process.

The response time of the solution is very good. We can change or take action on change requests very easily and that can be accessed at any time for all users and from all development sides.

I have used the solution within the last 12 months.

The solution is stable.

The initial setup is straightforward. The implementation was completed within one month.

I give the solution a nine out of ten.

As of this time, I have not encountered any areas for improvement for Microsoft Dynamics AX. I have not explored the solution in its entirety.

There are over 500 people using the solution.

I recommend the solution for any organization where Microsoft Dynamics AX meets its requirements.

Microsoft Dynamics AX product is an ERP solution. We provide this solution to three categories. One of them is the supply chain, one finance, and the other, retail commerce. We are implementing the supply chain through a simple warehouse model, which is finance-based. This includes the general ledger and other accounting functions. We are providing solutions for cash registers and E-commerce alongside other back-office solutions.

We currently work with retail companies in Turkey. We have implemented the biggest retail company which are apparel companies and grocery companies. These companies sell 40 products, worldwide. There's a lot of change currently happening in the business. For example, there are lots of new features, new functionalities, and lots of new requests from the business side. Existing local solutions cannot handle this, or change it. All local companies and enterprise industries need new functionality to adapt to the market. Hence, there is a good business case to use Microsoft Dynamics AX. You can expand it with open-source code with the partners. This gives the customers options to extend and manage their business.

Customers want all the business flow to be contained within the application. If they're using a lot of Excel and other documents, in addition to working with several other third-party applications, the problem is that these applications cannot integrate. That's a huge problem for business. It's possible to provide a solution to this by using an interconnected ERP solution with Dynamics. It is possible to interconnect to other products such as SAP, Oracle, and other global ERP types. Microsoft Dynamics AX makes this possible. Dynamics AX provides a lot of functionality. You have all your information to hand in one application. The application provides these values into the accounting application, and the accounting application executes the rest of the workflow. It's completely integrated. This is a huge and flexible design for customers.

Flexibility with how it is used. For example, if you have a specific way of working, Dynamics AX may or may not accommodate that. Although it provides a whole solution you may have to adapt your working methods to suit the product, and not how you would like to work. Sometimes the data forms provided for specific retail applications are not adequate and do not provide enough functions as the product itself is not designed for the retail industry it is mainly designed for automotive companies and distribution companies although Microsoft tried to add a retail element into the system. The product is standardised across industries so it is not a good fit for all types of sectors.

We have been working with Microsoft using this solution for about 12 years. We are a gold partner in Turkey, and we've implemented this solution in Turkey. We have also implemented this solution in Sweden. We support the old versions. The first version we used is the AX 2009 but today we are implementing the latest versions. We prefer to implement the solution in the cloud, although for economic reasons, some customers require the on-premises solution.

Premium support is good for the Microsoft aspect, but cloud support is not quite as good. They usually resolve issues very quickly, but sometimes do not provide key information when it is required by customers. This sometimes leads to clashes between partners and customers, as the partner is acting as first-line support.

The time it takes is mainly due to industry type and customers expectations. Customers often make a big mistake during implementation by not providing business logic upfront when it is required. Once it is known they start to test the application to make sure it is suitable for the business logic. They are in a rush to implement ERP. Some management consulting services companies are ignored during the project implementation. We usually implement Microsoft Dynamics AX within two months. Ultimately, it depends on the customer's expectations, not how can we manage, or design the solution. This can cause a delay in implementation times, and project timelines are increased. For example, in retail, an implementation can take just 2 months or 2 years. Retail business company's logic can be different from each other. The implementation part is easy if you know your business logic but if you don't know, it can take between 1 to 3 years to implement.

In Turkey, implementation has been difficult, as our customers are trying to reduce their IT personnel, and they want to push these services to the partners. This means the partners do not have experienced IT staff to liaise with on the implementations. The partners tend to use senior-level IT personnel working freelance, as it is not sustainable to pay the level of salaries they require permanently.

There are about 50 to 100 users, generally at each company. One of our customers has 200 stores. There's a lot of users when you calculate the number of users at each site. We negotiate licences with Microsoft. Microsoft provides a premium support agreement with partners. It's expensive for my country, Turkey. It's too expensive for customers to take this on themselves. As partners, we will buy this on behalf of the customers and then charge this value for each project.

The solution is good. I would give Microsoft Dynamics AX 8 out of 10.

Of the majority of projects I was involved in, two of them were for retail. They wanted to use it for the POS. One was a distribution company and one was for the production. They were importing and repacking some goods, FMCG goods, and selling them. The product was used mostly in scenarios of that type.

It's good for retail businesses. 

It expands a lot and constantly bringing on new features. It's got a lot of competitive features. 

The stability is okay.

There's a moderate amount of scalability available. 

They've put in asset management, which has been a nice improvement. 

The solution could be simplified and streamlined a bit. 

There should be more clarity and better functionality in the master planning features.

It's not easy to set up.

It would be ideal if the product was priced at a bit less.

The solution in general just needs a few quality improvements. 

I'm finding that often on-premises versions are getting left behind and new features more often are getting prioritized for the cloud. It's my understanding that they are doing this to push clients over to the cloud. 

I've used the solution for four or more years on multiple projects.

The stability is very good for the most part. Business 365 is a better solution on the stability front, however, I can't recall dealing with bugs or glitches and I can't recall it crashing or freezing.

The scalability is okay, however, S4HANA is more scalable than this product. Even with the POS version, if we go above a certain limit, we can have performance issues. The AX is scalable to the mid-level market and mid-level customers. 

The technical support from Microsoft is not bad. Normally, they are cooperative people. Normally in these kinds of software companies, they have their roadmap.  The support is rather satisfactory. We're happy with them.

I have some experience with Microsoft.

The difference between SAP and Microsoft is that, with Microsoft, you have to do more development. In SAP, you do less development. If a company is good with a developer and comfortable with the developer, I would suggest the AX. If they have less IT infrastructure for coding and development, then it might be better to look at something simpler. 

It's not easy to set up. You have to see a lot of things, a lot of setups, to get the hang of it. On top of that, often there are a number of items that the company is not using, and you have to put the defaults in place for that. It's not easy to configure. 

I don't deal with the licensing or pricing side of things, and therefore can't speak to how much it costs or how often licensing comes due. It is likely mid-level pricing - not the cheapest, and not the most expensive. There are other options for smaller-scale businesses such as NetSuite or SAP Business One that likely cost less. 

I work as an implementor and a consultant and I partner with Microsoft and SAP.

In the country I work in, only on-premises solutions are possible. They are not going into cloud solutions at all.

I'd rate the solution an eight out of ten.

If a company has a good development infrastructure, and they have an in-house development team, for smaller software such as SAP Business One and NetSuite, you can go with one developer or fewer developers. However, with AX or Dynamics 365, normally you'd probably be best with three to four developers in-house.