Following results for the quarter ending March 31, 2016, Microsoft on Thursday announced the total revenue for the period was $22.1 billion GAAP (in accordance with generally accepted accounting principles), and $23.6 billion non-GAAP. While, operating income was $5.6 billion GAAP, and $7.1 billion non-GAAP. The net income came out at $4.8 billion GAAP, and $5.7 billion non-GAAP.
And diluted earnings per share was $0.61 GAAP, and $0.73 non-GAAP.
“Our results this quarter reflect the trust customers are placing in the Microsoft Cloud,” said Satya Nadella, chief executive officer. “From large multi-nationals to small and medium businesses to non-profits all over the world, organizations are using Microsoft’s cloud platforms to power their digital transformation.”
Also, on Thursday, Microsoft Azure IoT Gateway SDK packages made available, to streamline the developer experience, and enabling them to get started in minutes.
With the Gateway SDK’s modular architecture, “developers can program their own custom modules to perform specific actions,” writes the Azure team. Thanks to its flexible design, these modules can be created in your preferred language such as – Node.js, Java, C#, or C.
While, .NET Core NuGet packages are coming soon, the following packages are available as on today:
azure-iot-gateway — contains runtime core and auto-installs module dependencies’ packages for Linux or Windows. You’ll be able to run the Gateway sample app and start writing Node.js modules.
generator-az-iot-gw-module — provides Gateway module project scaffolding with Yeoman.
com.microsoft.azure.gateway/gateway-module-base lets you run Gateway sample app and start writing Java modules. It contains the Gateway runtime core and links to the module dependencies’ packages for Linux or Windows.
com.microsoft.azure.gateway/gateway-java-binding or interface. This package is required for both runtime and publishing.
Microsoft.Azure.Devices.Gateway — contains the Gateway runtime core.
Microsoft.Azure.IoT.Gateway.Module — includes the module dependencies required to run the Gateway sample app and write .NET Framework modules on Windows.
New enhancements to the Azure AD Pass Through Authentication Preview, making these capabilities even more secure, easier to use, and easier to administer are live today.
Pass-through authentication lets users sign in to your cloud apps while getting rid of the need to store any user passwords in the cloud or deploy new server infrastructure.
Some key improvements turned on into this release include:
- improved user sign-on security with public key / private key encryption between Azure AD and on-premises agents. That’s in addition to secure HTTPS, which is always used to transfer usernames and passwords.
- now support using any attribute, configured as Alternate ID in Azure AD Connect, as the username.
- easier deployment as now you only need to open two ports to deploy pass-through authentication—the standard ports 80 and 443.
Finally, Microsoft made the Azure Management Libraries for .NET generally available now for Compute, Storage, SQL Database, Networking, Resource Manager, Key Vault, Redis, CDN and Batch services.
You can get the Azure Management Libraries for .NET open source package at Github.