News

Adobe SaaS Offerings Depend Even More on Azure

From Microsoft Ignite: The partnership that kicked off between the two companies two years ago takes another leap forward into the cloud in a big way.

Microsoft's public Azure cloud will be the primary platform upon which Adobe's suite of software-as-a-service offerings will run. That was the big news that kicked off the company's annual Ignite conference for IT pros and developers. Adobe President and CEO Shantanu Narayen joined Microsoft's CEO Satya Nadella on stage in opening moments of the kickoff keynote session of Ignite, taking place all week in Atlanta.

It's the extension of a partnership that the two companies kicked off two years ago when they worked together to optimize Adobe's apps for Windows 10 and Microsoft's Surface PC tablet. In addition to running the Adobe Creative Cloud, Adobe Document Cloud and Adobe Marketing Cloud on Azure, the companies' new partnership includes optimizing the latter for the new Microsoft Dynamics 365 suite.

"We think there is an opportunity out of the box to provide integration for all of our joint customers to have one integrated sales and marketing service, Narayen said. For Microsoft, Adobe's decision to run its massive SaaS infrastructure on Azure is the latest major endorsement of Redmond's public cloud. Among other key customers using Azure include General Electric, Renault-Nissan, Tyco and Boeing, among others.

"This coming together of the intelligent cloud with transformative SaaS applications with creativity and marketing is a massive milestone," Nadella said. This latest pact between the two companies will lead to more integrated offerings tying Office 365 and Dynamics 365 to Adobe's respective offerings, though the two companies haven't elaborated on that point.

Quick Notes: Microsoft CVP Jason Zander announced that Windows Server 2016 will include Docker Engine for free. Microsoft's Worldwide Commercial Business EVP Judson Althoff announced a second technical preview of the Azure stack, one that can run on already-installed, mixed hardware datacenters, and an "AI supercomputer." More details to follow.

More news from Microsoft Ignite will be posted here and on Redmondmag.com all week, so check back daily.

About the Author

Jeffrey Schwartz is the editor of 1105 Media's Redmond magazine, an editor-at-large and columnist for Redmond Channel Partner magazine, and author of a blog covering enterprise cloud computing called The Schwartz Cloud Report. Earlier in his tenure with the Enterprise Computing Group of 1105 Media, he held senior editorial postions with Application Development Trends, Visual Studio Magazine and Redmond Developer News. He has covered all aspects of enterprise IT for more than two decades and has spent much of that time writing about mobile computing technology. Before joining 1105 Media’s Enterprise Computing group, he held several senior editorial roles with such publications as VARBusiness (now part of CRN), InternetWeek and CommunicationsWeek.

comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube