Microsoft Azure vs. Oracle Hyperion (legacy)

Azure is particularly well suited for enterprise environments with existing Microsoft investments, those that require robust compliance features, and organizations that need hybrid cloud capabilities that bridge on-premises and cloud infrastructure. In my opinion, Azure is less appropriate for cost-sensitive startups or small businesses without dedicated cloud expertise and scenarios requiring edge computing use cases with limited connectivity. Azure offers comprehensive solutions for most business needs but can feel like there is a higher learning curve than other cloud-based providers, depending on the product and use case.

Well suited: For use in multiple offices around the world. I was able to obtain financial reporting data from 5 foreign offices and then consolidate their data with 3 domestic USA offices to prepare a consolidated financial statement. Less Appropriate: Translating the financial value for consulting services could be a bit challenging because that required human interaction and judgement. It would have been great to be able to set up some software to be able to interpret this and let it run for all future project work revenue projection.

Incentivized

• Microsoft Azure is highly scalable and flexible. You can quickly scale up or down additional resources and computing power.
• You have no longer upfront investments for hardware. You only pay for the use of your computing power, storage space, or services.
• The uptime that can be achieved and guaranteed is very important for our company. This includes the rapid maintenance for security updates that are mostly carried out by Microsoft.
• The wide range of capabilities of services that are possible in Microsoft Azure. You can practically put or create anything in Microsoft Azure.

Incentivized

• This product handles budgeting by Employee and/or Position very well. It is highly flexible and allows Hyperion administrators the ability to develop a planning application that fits a variety of different business needs.
• It is great at calculating benefits using business rules to automate the population of these fringe costs in the overall budget planning process. This greatly reduces user error.
• It allows you to seed the operating budget based on changes to key drivers, such as percentage increases, flat dollar increases and more detailed changes using business rules.
• Allows visibility into the plans for each unit across the organization, rolled up into an overall budget for the campus.
• It handles the creation of budgets with multiple chartfield segments or dimensions, which most other budgeting systems cannot handle well. It can aggregate these very quickly.

Incentivized

• The cost of resources is difficult to determine, technical documentation is frequently out of date, and documentation and mapping capabilities are lacking.
• The documentation needs to be improved, and some advanced configuration options require research and experimentation.
• Microsoft's licensing scheme is too complex for the average user, and Azure SQL syntax is too different from traditional SQL.

• One pain point for us is the consolidation and translation process. Needing to translate the data over and over again is frustrating and there is no visibility into how many users are running a translation. If multiple users attempt to translate the same data set, say goodbye to your performance but you have no way of knowing! (Unless you want to pull up a task audit which is not a very realistic expectation). It has the been the quickest way for us to bring the system to it's knees. The consolidation process performs in direct correlation to the complexity of the calculation/consolidation rules. So, while the product is extremely flexible, you still have to be careful how you design your rules and calculations to make sure that you do it on the smallest subset of data as possible to avoid large processing times. This makes sense, but requires some significant expertise that most organizations do not have in-house.
• The Hyperion Financial Reporting product is ridiculously outdated and clunky to use. The interface for designing reports is not intuitive, and not easy to modify once a report is built. I think there must be a strategic decision to move away from it and go to something more like Oracle BI because I just can't understand why in the world they don't update the reporting product. It also requires a significant level of expertise to be able to use. Not a great solution at all if you want multiple end-users to create reports in something other than Excel. Nobody except the HFM admin (which I used to be) in our company even touches this module.
• Another pain point is the amount of IT support that is required to run this thing, and again, specialized knowledge of Hyperion products and how they work is required for IT to adequately support it. This goes for application servers and the Oracle database that the applications are running on.

Moving to Azure was and still is an organizational strategy and not simply changing vendors. Our product roadmap revolved around Azure as we are in the business of humanitarian relief and Azure and Microsoft play an important part in quickly and efficiently serving all of the world. Migration and investment in Azure should be considered as an overall strategy of an organization and communicated companywide.

We're in the middle of the road because we are not sure that other products on the market fit the bill for what we need yet. Hyperion is expensive and burdensome from an administrator and maintenance standpoint, but it still seems to be the best solution for what we need. Show us an equally capable SaaS consolidation product and we'll talk again.

As Microsoft Azure is [doing a] really good with PaaS. The need of a market is to have [a] combo of PaaS and IaaS. While AWS is making [an] exceptionally well blend of both of them, Azure needs to work more on DevOps and Automation stuff. Apart from that, I would recommend Azure as a great platform for cloud services as scale.

Incentivized

It has proven to be unreliable in our production environment and services become unavailable without proper notification to system administrators

Incentivized

We were running Windows Server and Active Directory, so [Microsoft] Azure was a seamless transition. We ran into a few, if any support issues, however, the availability of Microsoft Azure's support team was more than willing and able to guide us through the process. They even proposed solutions to issues we had not even thought of!

Incentivized

The premium support team provides much needed dedicated customer service which we are after for what we have paid for this service. We are satisfied with the service and support and do not have any instance where there was an issue that requires escalation to get the right support team. Though the incidence of major issues that requires the premium support are less, we prefer to keep this as a safety net.

Incentivized

As I have mentioned before the issue with my Oracle Mismatch Version issues that have put a delay on moving one of my platforms will justify my 7 rating.

As I continue to evaluate the "big three" cloud providers for our clients, I make the following distinctions, though this gap continues to close. AWS is more granular, and inherently powerful in the configuration options compared to [Microsoft] Azure. It is a "developer" platform for cloud. However, Azure PowerShell is helping close this gap. Google Cloud is the leading containerization platform, largely thanks to it building kubernetes from the ground up. Azure containerization is getting better at having the same storage/deployment options.

Incentivized

I use Oracle Hyperion Enterprise Performance Mangement because the company I work at requires me to use it in the Financial Planning sector as most of their data is stored in it. I am open minded and ready to use other performance management tools created by Oracle if my work permits.

Incentivized

• For about 2 years we didn't have to do anything with our production VMs, the system ran without a hitch, which meant our engineers could focus on features rather than infrastructure.
• DNS management was very easy in Azure, which made it easy to upgrade our cluster with zero downtime.
• Azure Web UI was easy to work with and navigate, which meant our senior engineers and DevOps team could work with Azure without formal training.

Incentivized

• Oracle Hyperion allows us to automate and consolidate financial data that used to be performed manually in spreadsheets. From that perspective the ROI is huge.
• Oracle Hyperion functionality is extensive and allows us to perform most functions for planning, consolidating and reporting on our financial data.
• One negative with Oracle Hyperion is that it is complicated to implement and maintain. It takes expertise at all levels (infrastructure and management) to realize the benefits from it.

Incentivized