Azure Stream Analytics query testing now available in the new portal

Azure Stream Analytics is a fully managed service allowing you to gain insights and run analytics in near real-time on your big data streaming workloads. The service was first deployed more than 2 years ago, long before the “new” Azure management portal, http://portal.azure.com, even existed.

For the past few months we’ve been hard at work adding exciting new features to the service as well as transitioning the management user interface from the old https://manage.windowsazure.com to the new portal

Today we want to announce that we’ve just added the ability to test queries in the “new” portal without needing to start or stop a job. Here’s a quick look at how this works.

Setup

You can setup a Stream Analytics by following this simple tutorial – How to create a Stream Analytics job. 

Once you have created a new Stream Analytics job you would typically Create Inputs and then Create Outputs. Or you can just skip ahead to building the query and once your query is working then go back and define the Inputs and Outputs to match those used in the query. Both ways work, giving you the flexibility to decide how you wish to work.

For the purposes of this blog post I have defined a job with 1 data stream input, called StreamInput and 1 output, called Output. You can see these in the query editor blade above.

Open the Query editor blade from the job details screen by clicking on the query in the “Query” lens. Or in our case the < > placeholder because there is no query yet.

You will be presented with the rich editor as before where you create your query. This blade has now been enhanced with a new pane on the left. This new pane shows the Inputs and Outputs used by the Query, and those defined for this job.

There is also 1 additional Input and Output shown which I did not define. These come from the new query template that we start off with. These will change, or even disappear all together, as we edit the query. You can safely ignore them for now.

A key requirement and a common ask from our customers while writing a query is being able to test, and test often, to ensure that the output is what it is expected to be, given some input data. Having to save the query after every edit, start the job, wait for incoming data, check the results, and then stop the job again each time you make a small change to the query would be slow and is sometimes not even possible. A way to test changes to a query quickly was needed.

I am happy to announce that with today’s latest release in the portal you can now test the query without going through this stop/start process. Here&;s how …

Sample data and testing queries

To test with sample input data, right click on any of your Inputs and choose to Upload sample data from file.

Once the upload has completes you can then use the Test button to test this query against the sample data you have just provided.

The output of your query is displayed in the browser, with a link to Download results should you wish to save the test output for later use. You can now easily and iteratively modify your query, and test repeatedly to see how the output changes.

In the diagram above you can see how I have changed the query inline to have a 2nd output, called HighAvgTempOutput where I am only writing a subset of the data being received.
With multiple outputs used in a query you can see the results for both outputs separately and easily toggle between them.
Once you are happy with the results in the browser, then you can save your query, start your job, sit back and watch the magic of Stream Analytics happen for you.

Feature Parity and the road ahead

With the long awaited addition of sample data and query testing in the new portal we are happy to announce that we have reached feature parity between the portals. Everything you could do before, and more, is now in the new portal. Going forward all new development efforts will be concentrated on the new portal. The old portal will continue to work and existing functionality will remain until end of the calendar year when we place to completely retire support for Stream Analytics in the old portal.
If you have not tried Stream Analytics in the new portal we encourage you to head over and give it a try.

Next Steps

We’re really excited to bring local testing to the new portal and take this final step to reaching feature parity across the two portals. We hope this makes your life much easier as you go about developing (and testing) your queries.

We invite you to provide feedback on our User Voice page about what you want added next to the service!

If you are new to either Microsoft Azure or Stream Analytics, try it out by signing up for a free Azure trial account and create your first Stream Analytics job.

If you need help or have questions, please reach out to us through the MSDN or Stackoverflow forums, email the product team directly.
Quelle: Azure

Azure PowerShell 3.0.0–Highlights and breaking changes

Azure PowerShell is a set of PowerShell cmdlets which assist you in managing your assets in Azure using Azure Resource Manager (ARM) and Azure Service Management (RDFE).  Azure PowerShell 3.0.0 adds various improvements and fixes across multiple Azure resources; however, in accordance with semantic versioning, the introduction of a new major revision indicates breaking changes in a small subset of our cmdlets.  You can install the cmdlets via your favorite installation path indicated in the Azure PowerShell 3.0.0 release notes.

Resource improvements

ApiManagement

Enable support of Importing and Exporting SOAP based APIs (Wsdl Format)

Import-AzureRmApiManagementApi
Export-AzureRmApiManagementApi

Deprecated cmdlet Set-AzureRmApiManagementVirtualNetworks. In place, place used cmdlet Update-AzureRmApiManagementDeployment
Enabled support for ARM based VNETs for configuration Vpn via cmdlet Update-AzureRmApiManagementDeployment
Introduced support for VpnType (None, External, Internal) to differentiate ApiManagement workloads for Internet and Intranet
Fixed PowerShell issues


Batch

Added new cmdlet for reactivating tasks

Enable-AzureBatchTask

Added new parameter for application packages on job manager tasks and cloud tasks

New-AzureBatchTask -ApplicationPackageReferences

Added new parameters for job auto termination

New-AzureBatchJob -OnAllTasksComplete -OnTaskFailure
New-AzureBatchJob -ExitConditions

ExpressRoute

Added new parameter service key in return object when provider list all cross connection

Get-AzureCrossConnectionCommand

MachineLearning

Get-AzureRmMlWebService supports paginated response
Remind user Get-AzureRmMlWebService "Name" parameter needs to work with "ResourceGroupName" parameter

Network

Added new cmdlet to get application gateway backend health

Get-AzureRmApplicationGatewayBackendHealth

Added support for creating UltraPerformance sku

New-AzureRmVirtualNetworkGateway -GatewaySku
New-AzureVirtualNetworkGateway -GatewaySku

RemoteApp

Added cmdlets to enable User Disk and Gold Image Migration feature

Export-AzureRemoteAppUserDisk
Export-AzureRemoteAppTemplateImage

SiteRecovery

New cmdlets have been added to support one to one mapping with service objects.

Get-AzureRmSiteRecoveryFabric
Get-AzureRmSiteRecoveryProtectableItem
Get-AzureRmSiteRecoveryProtectionContainerMapping
Get-AzureRmSiteRecoveryRecoveryPoin
Get-AzureRmSiteRecoveryReplicationProtectedItem
Get-AzureRmSiteRecoveryServicesProvider
New-AzureRmSiteRecoveryFabri
New-AzureRmSiteRecoveryProtectionContainerMapping
New-AzureRmSiteRecoveryReplicationProtectedItem
Remove-AzureRmSiteRecoveryFabric
Remove-AzureRmSiteRecoveryProtectionContainerMapping
Remove-AzureRmSiteRecoveryReplicationProtectedItem
Remove-AzureRmSiteRecoveryServicesProvider
Set-AzureRmSiteRecoveryReplicationProtectedItem
Start-AzureRmSiteRecoveryApplyRecoveryPoint
Update-AzureRmSiteRecoveryServicesProvider

Following cmdlets have been modified for to support one to one mapping with service objects.

Edit-AzureRmSiteRecoveryRecoveryPlan
Get-AzureRmSiteRecoveryNetwork
Get-AzureRmSiteRecoveryNetworkMapping
Get-AzureRmSiteRecoveryProtectionContainer
Get-AzureRmSiteRecoveryStorageClassification
Get-AzureRmSiteRecoveryStorageClassificationMapping
Start-AzureRmSiteRecoveryCommitFailoverJob
Start-AzureRmSiteRecoveryPlannedFailoverJob
Start-AzureRmSiteRecoveryTestFailoverJob
Start-AzureRmSiteRecoveryUnplannedFailoverJob
Update-AzureRmSiteRecoveryProtectionDirection
Update-AzureRmSiteRecoveryRecoveryPlan

HUB support added to Set-AzureRmSiteRecoveryReplicationProtectedItem.
Deprecation warning introduced for cmlets/parameter-sets which does not comply to SiteRecovery service object model.

Breaking changes

Data Lake Store

The following cmdlets were affected this release (PR 2965):

Get-AzureRmDataLakeStoreItemAcl (Get-AdlStoreItemAcl)

This cmdlet was removed and replaced with Get-AzureRmDataLakeStoreItemAclEntry (Get-AdlStoreItemAclEntry).
The old cmdlet returned a complex object representing the access control list (ACL). The new cmdlet returns a simple list of entries in the chosen path&;s ACL.

# Old
Get-AdlStoreItemAcl -Account myadlsaccount -Path /foo

# New
Get-AdlStoreItemAclEntry -Account myadlsaccount -Path /foo

Get-AzureRmDataLakeStoreItemAclEntry (Get-AdlStoreItemAclEntry)

This cmdlet replaces the old cmdlet Get-AzureRmDataLakeStoreItemAcl (Get-AdlStoreItemAcl).
This new cmdlet returns a simple list of entries in the chosen path&039;s ACL, with type DataLakeStoreItemAce[].
The output of this cmdlet can be passed in to the -Acl parameter of the following cmdlets:

Remove-AzureRmDataLakeStoreItemAcl
Set-AzureRmDataLakeStoreItemAcl
Set-AzureRmDataLakeStoreItemAclEntry

# Old
Get-AdlStoreItemAcl -Account myadlsaccount -Path /foo

# New
Get-AdlStoreItemAclEntry -Account myadlsaccount -Path /foo

Remove-AzureRmDataLakeStoreItemAcl (Remove-AdlStoreItemAcl), Set-AzureRmDataLakeStoreItemAcl (Set-AdlStoreItemAcl), Set-AzureRmDataLakeStoreItemAclEntry (Set-AdlStoreItemAclEntry)

These cmdlets now accept DataLakeStoreItemAce[] for the -Acl parameter.
DataLakeStoreItemAce[] is returned by Get-AzureRmDataLakeStoreItemAclEntry (Get-AdlStoreItemAclEntry).

# Old
$acl = Get-AdlStoreItemAcl -Account myadlsaccount -Path /foo
Set-AdlStoreItemAcl -Account myadlsaccount -Path /foo -Acl $acl

# New
$aclEntries = Get-AdlStoreItemAclEntry -Account myadlsaccount -Path /foo
Set-AdlStoreItemAcl -Account myadlsaccount -Path /foo -Acl $aclEntries

ApiManagement

The following cmdlets were affected this release (PR 2971):

New-AzureRmApiManagementVirtualNetwork

The required parameters to reference a virtual network changed from requiring SubnetName and VnetId to SubnetResourceId in format/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ClassicNetwork/virtualNetworks/{virtualNetworkName}/subnets/{subnetName}

# Old
$virtualNetwork = New-AzureRmApiManagementVirtualNetwork -Location <String> -SubnetName <String> -VnetId <Guid>

# New
$virtualNetwork = New-AzureRmApiManagementVirtualNetwork -Location <String> -SubnetResourceId <String>

Deprecating Cmdlet Set-AzureRmApiManagementVirtualNetworks

The Cmdlet is getting deprecated as there was more than one way to Set Virtual Network associated to ApiManagement deployment.

# Old
$networksList = @()
$networksList += New-AzureRmApiManagementVirtualNetwork -Location $vnetLocation -VnetId $vnetId -SubnetName $subnetName
Set-AzureRmApiManagementVirtualNetworks -ResourceGroupName "ContosoGroup" -Name "ContosoApi" -VirtualNetworks $networksList

# New
$masterRegionVirtualNetwork = New-AzureRmApiManagementVirtualNetwork -Location <String> -SubnetResourceId <String>
Update-AzureRmApiManagementDeployment -ResourceGroupName "ContosoGroup" -Name "ContosoApi" -VirtualNetwork $masterRegionVirtualNetwork

Network

The following cmdlets were affected this release (PR 2982):

New-AzureRmVirtualNetworkGateway

Description of what has changed :- Bool parameter:-ActiveActive is removed and SwitchParameter:-EnableActiveActiveFeature is added for enabling Active-Active feature on newly creating virtual network gateway.

# Old
# Sample of how the cmdlet was previously called
New-AzureRmVirtualNetworkGateway -ResourceGroupName $rgname -name $rname -Location $location -IpConfigurations $vnetIpConfig1,$vnetIpConfig2 -GatewayType Vpn -VpnType RouteBased -EnableBgp $false -GatewaySku HighPerformance -ActiveActive $true

# New
# Sample of how the cmdlet should now be called
New-AzureRmVirtualNetworkGateway -ResourceGroupName $rgname -name $rname -Location $location -IpConfigurations $vnetIpConfig1,$vnetIpConfig2 -GatewayType Vpn -VpnType RouteBased -EnableBgp $false -GatewaySku HighPerformance -EnableActiveActiveFeature

Set-AzureRmVirtualNetworkGateway

Description of what has changed :- Bool parameter:-ActiveActive is removed and 2 SwitchParameters:-EnableActiveActiveFeature / DisableActiveActiveFeature are added for enabling and disabling Active-Active feature on virtual network gateway.

# Old
# Sample of how the cmdlet was previously called
Set-AzureRmVirtualNetworkGateway -VirtualNetworkGateway $gw -ActiveActive $true
Set-AzureRmVirtualNetworkGateway -VirtualNetworkGateway $gw -ActiveActive $false

# New
# Sample of how the cmdlet should now be called
Set-AzureRmVirtualNetworkGateway -VirtualNetworkGateway $gw -EnableActiveActiveFeature
Set-AzureRmVirtualNetworkGateway -VirtualNetworkGateway $gw -DisableActiveActiveFeature
Quelle: Azure

Keeping up with Azure Government: September Highlights

I’m super excited to recap a busy month of service launches and releases. This has been an extra busy month for us where we landed critical and key features that you all have been waiting for. We believe these updates provide a richer, more robust customer experience and are excited to bring these additional awesome products to the US Government market including: SQL v12, Redis Cache, Virtual Machine Scale Sets, A1-A7 VM series for ARM, D/DS VM Series for ARM and F-Series VMs for ARM, Service Fabric, Storage Service Encryption, Web Apps.

Specifically, major updates to the platform include:

Enhancements to Azure Government Resource Management (ARM), making it much easier to setup and configure your virtual machines and other services
SQL v12 allows users to focus on rapid app development and get rid of your need to worry about managing the VMs and infrastructure that support your SQL databases
Storage Service Encryption encrypts your data at rest to meet government security and compliance requirements
Bringing F-Series VMs to USGov Iowa

Other highlights from this month include:

Azure Government pricing is now in the pricing calculator allowing government consumers to better budget the use of Azure services.
Microsoft signing the CJIS security addendum for Oregon, which marked the 23rd state to the list of states that Microsoft supports for CJIS, more than any other cloud provider, making up the cloud leader in CJIS

To stay up to date on all things Azure Government, be sure to subscribe to our RSS feed and to receive emails by clicking “Subscribe by Email!” on the Azure Government Blog. To experience the power of Azure Government for your organization, sign up for an Azure Government Trial.
Quelle: Azure

TIBCO DataSynapse comes to the Azure Marketplace

We are pleased to announce the launch of TIBCO DataSynapse GridServer Engine – cloud edition in the Azure Marketplace. Available from today, this collaboration expands on the HPC burst work we have been doing with DataSynapse customers over the last few months to provide an easy deployment method in a cost effective manner.

Over the last 15 years TIBCO Software has been working to empower executives, developers and business users through the integration of applications and ecosystems to analyze data and create real-time solutions.

TIBCO DataSynapse GridServer is a service execution platform for dynamically scaling any application at any time across grid infrastructure. As a result of its improvement in productivity, performance and uptime to existing applications, it is used heavily within Financial Services for parallel computing certain risk calculations. By bringing DataSynapse GridServer Engine 6.2.0 to Azure, Microsoft its extending the possibilities of this platform by providing infrastructure flexibility, increased scalability and cost control.

The pay-as-you-go Marketplace image is intended for those customers that have an existing GridServer DataSynapse installation on-premises and wish to extend the environment beyond its current capacity into Azure.

This solution provides one or more virtual machines in Azure which are configured to connect to the director, the IP and FQDN that are provided at the time the Marketplace offering is purchased. The solution assumes that the customer is either running one or more on-premises managers and has a VPN connection between their Azure account and their managers already set up, or they are running their grid in Azure and already have a virtual network to which they intend to add the engine VM.

TIBCO has provided the option of installing the image on three VM families, A-series, D-series and Dv2. This was intended to give customers a range of price vs. performance and appeal to a number of different workloads.

"Microsoft Azure and TIBCO have worked closely together to deliver the perfect solution that combines Azure&;s compute resources with TIBCO&039;s Datasynapse Grid Server in a pay-as-you-go model. This enables our investment banking customers to tackle new regulations, such as Basil III&039;s FRTB and meet the large compute demands."

                                                                                                     – Mike Kennedy – TIBCO Sr. Director of Engineering

We are excited to see the continued development of DataSynapse GridServer for use with critical compute workloads and enable the benefits of the scale and elasticity of the Azure cloud. Further information on this release can be found here.

 
Quelle: Azure

Azure Backup hosts Ask Me Anything session

The Azure Backup team will host a special Ask Me Anything session on /r/Azure, Thursday, October 20, 2016 from 09:00 am to 1:00 pm PDT.

What&;s an AMA session?

We&039;ll have folks from across the Azure Backup Engineering team available to answer any questions you have. You can ask us anything about our products, services or even our team!

Why are you doing an AMA?

We like reaching out and learning from our customers and the community. We want to know how you use Azure and Azure Backup and how your experience has been. Your questions provide insights into how we can make the service better.We did this last year and we are excited about the questions and feedback we have received and we are doing it again.

Who will be there?

You, of course! We&039;ll also have PMs and Developers from the Azure Backup team participating throughout the day.
Have any questions about the following topics? Bring them to the AMA.

•    Backup of Azure IaaS VMs (both Classic and Resource Manager VMs)
•    Azure Backup Server
•    System Center Data Protection Manager (We announced VMware VM backup support couple of months ago)
•    Microsoft Azure Recovery Services Agent

Why should I ask questions here instead of StackOverflow, MSDN or Twitter? Can I really ask anything?

An AMA is a great place to ask us anything. StackOverflow and MSDN have restrictions on which questions can be asked while Twitter only allows 140 characters. With an AMA, you’ll get answers directly from the team and have a conversation with the people who build these products and services.

Here are some question ideas:
•    What is Azure Backup? What is the cloud-first approach to backup?
•    How should I choose between Azure Backup Server and System Center Data Protection Manager for my application backup?
•    What are the pros/cons of using VM backup versus File/Folder backup?
•    How does the “Protected Instances” billing model work?
•    Why should I pick cloud over tape for long term retention?
•    What can be protected in Recovery Services vault?

Go ahead, ask us anything about our public products or the team. Please note, we cannot comment on unreleased features and future plans.

Join us! We&039;re looking forward to having a conversation with you!
Quelle: Azure

Microsoft Common Controls Hub provides uncommon convenience

In an effort to push the envelope for providing our customers transparency and a top grade compliance experience, I’d like to to announce a compliance tool newly available through the Microsoft Trust Center for Azure; the Common Controls Hub powered by Unified Compliance. This customized Microsoft portal lets you compare control frameworks across a number of compliance mandates and privacy regimes including ISO 27001, SOC 1 and 2, PCI, FedRAMP, EU Model Clauses, hundreds of geographic-specific requirements, and many others.

We’ve arranged for any Microsoft customer (Azure, Office 365, CRM, or others) to create a free account to access a Microsoft-curated library of complete standards guidance. You’ll see control descriptions and objectives, have the ability to map requirements from one framework to another, and gain a deeper understanding of any gaps in your own compliance activities.

Best of all, these frameworks are maintained for you! Researchers are constantly revising the source data based on updates to the standards, and ensuring default mappings stay relevant. You can build a custom controls list to help guide your own security and audit efforts, and once you have narrowed down the set of controls that are applicable to your environment, you can track your status against them.

The Microsoft Common Controls Hub is another step in providing the cloud industry’s highest levels of transparency and compliance with international standards. In addition to assessments and attestations against more than 45 different certifications, laws, and regulations, Azure remains committed to enabling our customers to achieve compliance with their own industries’ mandates and regional requirements.
Quelle: Azure

Azure IoT Gateway SDK integrates support for Azure Functions

At Microsoft, we believe the edge of the network plays a critical role in IoT, not only in IoT devices themselves but also in intermediate field gateways.  Earlier this year, we announced the open source Azure IoT Gateway SDK, our approach to accelerating the development of IoT edge scenarios such as supporting legacy devices, minimizing latency, conserving network bandwidth, and addressing security concerns.  Since then, we’ve been busy improving and enhancing our SDK completely out in the open.

Today, we are happy to announce an exciting new capability we’ve added to the IoT Gateway SDK: Support for Azure Functions.  With Azure Functions integration, developers can easily call cloud-based logic from their IoT gateway. Just write an Azure Function and you can quickly call it from a Function Module in the Azure IoT Gateway SDK.

For example: if something goes wrong in your field gateway environment, such as local devices that can’t connect or misbehave, and you want to upload diagnostic information to your Azure IoT solution for inspection by operations, our new Functions integrations makes this simple. Just create an Azure Function that takes this data, stores it and alerts operations – and then call it from your gateway running the Azure IoT Gateway SDK when you encounter a problem.

The Azure IoT Gateway SDK supports everything from low-level modules written in C to connect the broad variety of deployed devices, to high level modules for productivity such as our new Azure Functions support.  The best part of the Azure IoT Gateway SDK is how easy it is to chain these modules together to create reusable processing pipelines that suit your needs.

We’ve already seen some great success stories from businesses benefitting from our approach to edge intelligence, and we’re looking forward to seeing what our customers and partners will create with this exciting new capability.
Quelle: Azure

Azure compliance white paper-o-rama

Following national and regional regulations of the countries your business operates in is not an easy task, yet it is an absolute necessity as businesses across all industries see their customer bases expand geographically. Whether you’re a business or an organization operating within the boundaries of a single country or across the globe, you can confidently move to the cloud and still maintain alignment with regional and international requirements. To help our customers understand how to deploy in Azure while successfully interpreting US and international governance requirements, we produced a series of documents that can be leveraged during your cloud adoption journey.

The following white papers include guidance for US law enforcement, US education, UK G-cloud, and Cloud services in Germany, Malaysia, New Zealand, Singapore, and Australia. These papers shed light on the nuances we want our customers to be aware of when interacting with government or regional authorities as it relates to adopting Azure cloud services.
 
Here&;s a short summary of our most recently produced white papers:

 The CJIS Implementation Guidelines for Azure Government, Office 365 Government, Dynamics CRM Online Government white paper is designed to provide insight into the Criminal Justice Information Services (CJIS) security controls applicable to Microsoft Cloud services, and provide guidance to law enforcement agencies on where to access detailed information to assist in CJIS audits. This document provides guidelines and resources to assist CJIS Systems Agencies (CSA) and law enforcement agencies (LEA) in implementing and utilizing Microsoft Government Cloud features, which meet the applicable CJIS certification standards and are consistent with FBI CJIS Security Policy.
The FERPA Implementation Guide for Microsoft Azure white paper helps educational organizations that are considering a move to Azure and are looking for guidance in designing and operating solutions that incorporate security controls to help them meet their compliance challenges. This paper provides insight into how Microsoft meets its compliance obligations on the platform and presents best practices and security principles that are aligned to the Family Educational Rights and Privacy Act (FERPA), International Organization for Standardization (ISO) 27001, Microsoft’s Security Development Lifecycle (SDL), and operational security for online security.  
The Microsoft Cloud Germany for commercial customers in the European Union (EU) and European Free Trade Association (EFTA) white paper provides guidance on how to store and manage customer data in compliance with applicable German laws and regulations as well as key international standards. By leveraging the Microsoft developed data trustee model that provides and enables European customers to move to the cloud, EU and EFTA customers can achieve compliance while utilizing Azure cloud services.
The Microsoft Azure Compliance in the context of Malaysia Security and Privacy Requirements white paper addresses Malaysian regional compliance matters in the context of Malaysia Security and Privacy Requirements. Read this white paper to learn more about the questions faced by customers in Malaysia who are considering a move to the cloud.
The Microsoft Azure Compliance in the context of New Zealand Security and Privacy Requirements white paper is written for IT decision makers in New Zealand who are considering whether to move their data to Microsoft Azure. This paper addresses questions like: Does Microsoft Azure meet New Zealand’s compliance requirements? Where is data stored and who can access it? What is Microsoft doing to protect data? How can a customer verify that Microsoft is doing what it says? New Zealand organizations in need of meeting compliance requirements can read this paper to learn about Azure key security and privacy principles that will enable them to meet their compliance goals.
The Microsoft Azure Compliance in the context of Australia Security and Privacy Requirements white paper is written for Australian organizations looking to navigate their country-specific security and privacy requirements. Protecting data, monitoring and securing access, and meeting customer promises are achieved by Azure through implementing security and privacy principles, enabling Australian customers to leverage our cloud offerings with confidence. 
The Microsoft Azure Compliance in the context of Singapore Security and Privacy Requirements white paper addresses the Singapore standards Multi-Tier Cloud Security (MTCS) and how Microsoft complies with the Singapore Personal Data Privacy Act (PDPA). This means both government and commercial customers can have confidence knowing they comply with Singapore legislative and certification requirements when deploying data to the cloud.
The 14 Cloud Security Controls for UK cloud using Microsoft Azure white paper provides customer strategies on moving their services to Azure while meeting their UK obligations mandated by the CESG/NSCS. Customers of the UK can learn how Azure can be used to help address the 14 controls outlined in the cloud security principles. This paper also outlines how customers can move faster and achieve more while saving money as they adopt Azure cloud services.

These white papers represent a set of new guidance created to help customers understand local laws and governance issues, and provide insight into the local regulatory requirements when deploying to the cloud. Check out these papers as well as other useful guidance on the Microsoft Trust Center.
Quelle: Azure

Database collation support for Azure SQL Data Warehouse

We’re excited to announce you can now change the default database collation from the Azure portal when you create a new Azure SQL Data Warehouse database. This new capability makes it even easier to create a new database using one of the 3800 supported database collations for SQL Data Warehouse. Collations provide the locale, code page, sort order and character sensitivity rules for character-based data types. Once chosen, all columns and expressions requiring collation information inherit the chosen collation from the database setting. The default inheritance can be overridden by explicitly stating a different collation for a character-based data type. Changing collation To change the default collation, you simple update to the Collation field in the provisioning experience. For example, if you wanted to change the default collation to case sensitive, you would simply rename the Collation from SQL_Latin1_General_CP1_CI_AS to SQL_Latin1_General_CP1_CS_AS. Listing all supported collations To list all of the collations supported in Azure SQL Data Warehouse, you  can simply connect to the master database of your logical server and running the following command:SELECT * FROM sys.fn_helpcollations();
This will return all of the supported collations for Azure SQL Data Warehouse. You can learn more about the sys.fn_helpcollations function on MSDN.
Checking the current collation
To check the current collation for the database, you can run the following T-SQL snippet:SELECT DATABASEPROPERTYEX(DB_NAME(), ‘Collation’) AS Collation;
When passed ‘Collation’ as the property parameter, the DatabasePropertyEx function returns the current collation for the database specified. You can learn more about the DatabasePropertyEx function on MSDN.
Learn more
Check out the many resources for learning more about SQL Data Warehouse, including:

What is Azure SQL Data Warehouse?
SQL Data Warehouse best practices
Video library
MSDN forum
Stack Overflow forum
Quelle: Azure

Introducing the 2016 Future of Cloud Computing Survey – Join the cloud conversation

North Bridge, a leading venture capital firm, Wikibon, a worldwide community of practitioners, technologists and consultants dedicated to improving the technology adoption, have partnered to launch the sixth annual Future of Survey.

Microsoft participates in this survey regularly because your feedback on cloud computing is important to us and the industry. We want to hear about your plans for cloud, where it is making an impact across your organization, and what cloud technologies and capabilities you are prioritizing in your business.

We invite you to be among the first to TAKE THE SURVEY and share it with your network. By doing so you will help all of us in the industry get a better view on what customers are doing with cloud computing and identify emerging trends.

Results of the survey will be announced later this year and we will be back here to share the findings with you in November.

We look forward to hearing from you!
Quelle: Azure