Today, at Microsoft’s Build developer conference, Pivotal announced the general availability (GA) of support for Microsoft Azure Stack will ship with Pivotal Cloud Foundry 2.2.
According to Microsoft’s own research, 84% of IT decision makers have a hybrid cloud strategy and 91% say hybrid cloud is here for the long-term. For many IT leaders, their hybrid cloud approach ends up as a unique combination of their existing on-premises infrastructure and preferred public cloud vendor. However, this practical, evolutionary approach can be problematic, requiring challenging cloud integrations for key capabilities such as identity, management and security, data services and application development. Developers and IT also have the overhead of learning to work with (at least) two environments.
While other public clouds and on-premises technology providers look to ease this situation with offerings that extend customers’ existing datacenter investments into the public cloud, Microsoft’s vision is the reverse. They bring the Azure public cloud model back on-premises for consistent operations, management, and applications. This is the goal of Azure Stack, now shipping.
#AzureStack is the diverse & trusted #Azure ecosystem "on your terms"says #CTO Mark Russinovich.#HybridIT #HPEMSFT #HybridCloud #DigitalTransformation #Cloud pic.twitter.com/V3WzpnSkW2— TechNative (@TechNative) February 5, 2018
PCF: Consistent PaaS for a Consistent Cloud
Moving up the cloud-native stack, Pivotal Cloud Foundry offers developers and operators a complementary, consistent platform-as-a-service layer on any datacenter or cloud IaaS, including Azure and Azure Stack.
Many customers already enjoy the choice, speed, and reliability of this powerful combination, including Ford, Manulife, and Merrill.
Cure developers’ infrastructure headaches, streamline ops
This combination gives developers the essential “cf push” experience across hybrid environments, deploying .NET and Java code to run on the platform without concern for where, or how, it’s running. Taking the infrastructure headaches away from developers means they can focus on delivering innovative applications that drive business results, and with PCF on Azure Stack it’s simple to deploy across their organization’s hybrid cloud. And with a single, consistent cloud platform to operate, IT and operations jobs are made easier as they use the same tools and technologies to manage the underlying platform for both Day 1 and Day 2 operations.
Private Cloud. Compelling hybrid cloud scenarios.
If you’re looking at Azure Stack with PCF for a purely on-premises “private cloud” solution then you’re missing out on the biggest benefit! The consistency and connectivity with public cloud Azure mean you can build your hybrid cloud strategy with confidence that developers and operators will be able to move between environments with the minimum friction and fuss.
Azure Stack with PCF forms the foundation for many hybrid cloud scenarios:
On-prem innovation, at cloud speed
You expect your public cloud to bring you the latest innovations and security fixes as soon as they’re available. So why lower your expectations for a hybrid solution? Both Azure Stack and Pivotal Cloud Foundry offer continuous, rolling updates on a cloud cadence.
Get started with PCF and Azure Stack today
Read about Dell EMC’s Cloud, optimized for Azure Stack
Learn about Azure Stack pricing and licensing
See how Pivotal Cloud Foundry and Azure work together
Discover more about how Pivotal helped build Ford Pass
Safe Harbor Statement - the preceding blogpost is intended to outline the general direction of certain of Pivotal's offerings. It is intended for information purposes only and may not be incorporated into any contract. Any information regarding the pre-release of Pivotal offerings, future updates or other planned modifications is subject to ongoing evaluation by Pivotal and is subject to change. This information is provided without warranty or any kind, express or implied, and is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions regarding Pivotal's offerings. These purchasing decisions should only be based on features currently available. The development, release, and timing of any features or functionality described for Pivotal's offerings in this blogpost remain at the sole discretion of Pivotal. Pivotal has no obligation to update forward-looking information in this blogpost.
About the AuthorFollow on Twitter Follow on Linkedin More Content by John Allwright