We make more money on cloud-based Exchange than legacy email

Per-user income greater in cloud, or so Microsoft claims

microsoft Claims it earns more money per user from cloud-based Exchange email accounts than it does selling the legacy version of Exchange Server most businesses deploy today.

MCTS Certification, MCITP Certification

Microsoft MCTS Certification, MCITP Certification and over 2000+
Exams with Life Time Access Membership at https:://www.actualkey.com

That’s what Microsoft investor relations GM Bill Koefoed said at the Oppenheimer Annual Technology, Media & Telecommunications Conference Tuesday, according to a transcript on Microsoft’s website. Customers who purchase Exchange as part of the Office 365 cloud service pay roughly $10 per month, less than they would in the back-end costs of running their own Exchange servers, but nearly all of of it goes directly to Microsoft, he said.

Hosted productivity suites: Google Apps or Microsoft Office 365?

That doesn’t mean Microsoft actually makes more money in the cloud than it does with its traditional business of selling software licenses. For one thing, Microsoft’s cloud customer base is mostly small businesses. To gain the kind of per-user profits Koefoed is talking about, Microsoft needs Office 365 to lure in big enterprises.

“Within an enterprise, let’s say it costs $15 per user per month today to run Exchange, and that’s about $2 for Microsoft, and that’s $13 in rent, power, the data base administrator that’s running the thing, the hardware and all the kind of services that are associated with kind of running Exchange in your premise,” Koefoed said.

“With Office 365, or with Exchange Online, the Exchange part of that, we charge $10 per user per month,” he continued. “So, that ends up being a savings to the CIO of roughly 33%, and we make 5X more revenue and our profit ends up being somewhere, $3 or $4 per user per month. So, we make more revenue and we make more profit and we save our customers money.”

The profit ends up being $3 or $4 per user per month because it costs Microsoft $6 or $7 per user to run the data centers powering the cloud service. “We can do that at scale,” Koefoed noted. “Interestingly, one of the things that we’ve learned in our search business is how to run data centers at scale.”

Koefoed gave the example in response to investors’ questions about how Microsoft’s revenue in the cloud compares to its traditional business model of selling software licenses. The popularity of Google Apps with small businesses is among the factors that forced Microsoft to expand its Web-based offerings, but investors are likely concerned these offerings will cannibalize Microsoft’s existing revenue streams.

Koefoed’s example leaves out the fact that Office 365 is appealing mostly to smaller businesses with few users. The small business version of Office 365, which includes Exchange, SharePoint, Lync and Office Web Apps, costs only $6 per user per month. An actual Exchange Server license, meanwhile, costs $700 for a standard edition and $4,000 for an enterprise edition, plus extra charges for client access licenses.

Enterprises can lessen the financial hit because of their scale, making the economics of running their own servers worthwhile for the customer, which is why Koefoed can say enterprises pay Microsoft only $2 per user per month to run Exchange. For small customers, the per-user cost of running Exchange Server without a cloud subscription would be higher, and therefore more profitable for Microsoft. Whether Microsoft actually makes more per-user profit from cloud services than packaged software is therefore questionable.

System Center Orchestrator 2012 – what’s changing?

OIS 6.3 is repackaged and given a facelift but remains fundamentally the same.

By Kerrie Meyler and Pete Zerger.  Now that System Center Orchestrator 2012 is available in beta, you may be wondering if it is worthwhile to continue creating policies with Opalis Integration Server (OIS) 6.3. Will you have to rewrite all your OIS policies for the next release?

 

Best Microsoft MCTS Training, Microsoft MCITP Training at certkingdom.com

This is a valid question, as Opalis Software’s first release of OIS was not compatible with its previous OpalisRobot offering. However, Robot had a different code base than OIS. This is not the case going from OIS 6.3 to Orchestrator 2012, as the underlying engine is not changing, and Microsoft has announced that policies built in OIS (unless they use Legacy objects), along with their data, are usable in Orchestrator. Of course, some things ARE changing; here is a quick look:

New Operator Console. The OIS console is based on Java, requires numerous downloads, and has a fairly painful installation. With Orchestrator, Microsoft has rewritten the console in Silverlight, and it now ships with the core product and uses typical Microsoft installation technology.

New Web Service. The Java-based Opalis web service is replaced by an OData web service. Invoking runbooks through this web service doesn’t seem to be documented yet.

Renaming. Here are some of the terminology changes with Orchestrator 2012:

Foundation objects become standard activities (and objects are now known as activities). These objects have updated, as have the icons for these objects.
Policies renamed to runbooks
Action server renamed to runbook server
Policy Testing Console becomes the Runbook Tester
Operator Console now the Orchestration Console

Changes in Foundation objects (now Standard activities).

Workflow Control category now called Runbook Control
Custom Start now Invoke Data
Publish Policy Data now Return Data
Trigger Policy now Invoke Runbooks
Notification Category – Send Page activity gone
System Category – Purge Event Log activity gone

WSDL gone. System Center Orchestrator 2012 uses a ReST-based Web Service so there is no WSDL. The web service supports OData, enabling easy management of the runtime environment.

Security. Updated cryptography and security model based on Microsoft best practices, allowing for centralized security management.

Operating environment for system components. Orchestrator must be installed on Windows 2008 R2 (SP1 is supported), and requires Microsoft SQL Server 2008 R2 for its database engine

No Oracle backend support. This should not be much of a surprise, given that Microsoft does not have a history of using Oracle for a database engine. System Center Opalis Integration Server 6.3 Unleashed warns that this was not anticipated to be a supported platform in the next release. And from what we’ve heard, the people who had to support it are happy it’s gone!

Although there is no longer support for Legacy objects – and their use was not recommended even in OIS 6.3 – the engine is still 32-bit and has not been re-architected. Other than some terminology changes, improved installation experience, and new consoles, the product remains fundamentally the same. This means that your policies will continue to work after you export them out of the Opalis environment and into the Orchestrator environment (presuming there are no legacy objects in the policies).

At the moment, Operations Manager 2012 and Orchestrator SCO 2012 work together, although most of the System Center 2012 beta products do not, and will not until MS produces updated IPs for them.

Figure 1 shows the new Orchestrator console, Figure 2 displays the .Net Orchestration Console and Web Service in IIS Manager.