Microsoft Azure vs Salesforce Lightning Platform (formerly Salesforce App Cloud)

• Azure Functions is the easiest serverless service to work with in my experience. Easy to ship Node.js functions without bundling dependencies.
• Proactive and responsive support. We've worked with most other cloud providers - Amazon, Google, Oracle. Amazon Web Services' customer support is a black hole and their documentation is worthless. Google and Oracle are better, but Azure's support is responsive and their docs are pretty good.
• Azure's Web UI is pretty easy to work with

Read full review

• Reporting and Dashboards are thorough and can show a wealth of important data to inform and scale processes. It's helpful in a high volume sales cycle to be able to quickly identify weak points in performance and productivity so that adjustments can be made.
• Highly customizable. We are able to customize just about everything which allows us to track very specific things and in theory create better efficiency.
• Parent/Child account hierarchy exists which is helpful.
• Contact records can be associated with multiple accounts and opportunities. This, in theory, should minimize duplicates and mismanagement of contacts.
• Console helps a lot with data nesting. Having a fairly comprehensive look at an account without searching through various tabs and sections speeds up an otherwise cumbersome platform.

Read full review

• Could be easier to setup redundancy
• Feels as if there are too many options, bells, and whistles you could add.
• Microsoft Azure functions does not have a "Configure Services" method. Programming Azure functions has a slightly different programming model than does a "normal" API application. I would prefer that the startup process be identical.

Read full review

• It can be a bit buggy at times, like randomly not letting you save or making you refresh the page or do the same action, and then it will save.
• Bugs really are the main issue here. Otherwise it's great with reporting!

Read full review

• It has taken a few years of planning and growth (which continue), but we've been able to successfully budget and plan for ever increased capacity by starting first with some Virtual Machines and factoring in on-prem maintenance vs cloud constant improvements. VM (server, compute, networking) costs even out quickly over time and will show savings very soon.
• Because of Azure Application Gateways (which cost very little to set up and maintain), we were able to build a state of the art single-sign-on hub for all of our users and other enterprise platforms (mostly non-Microsoft and non Azure systems), reducing the amount of time to switch among these for workers and increasing overall productivity.
• With Azure Active Directory, we do not need to maintain separate identity systems and can more easily integrate our organizations credentials into authorization for access to other systems.

Read full review

• This has been a huge time waster for our team.
• Load times are at least 3 times as long as they used to be.
• Our workflows can not be as efficient as they used to be so we spend more time doing manual tasks.
• More things have to be pushed through our ops team instead of being able to do them ourselves, which creates significant roadblocks.

Read full review