NEXT UP EXAM CAMPS - The next round starts September 4, Register Today!

Get hired, demonstrate clear business impact, and advance your skills with Microsoft certifications. During the last six months the Microsoft Next Up Exam Camps have helped over 250 individuals to upskill in vital cloud technologies and earn one of the Cloud Microsoft Certifications. Microsoft Next Up is a step-by-step exam camp that removes roadblocks, provides you…


海を隔てた米国と欧州のサイバーセキュリティ アプローチの違い

2017 年 5 月 17 日 – Paul Nicholas – Trustworthy Computing、シニア ディレクター このポストは「 More than just an ocean separates American and European approaches to cybersecurity 」の翻訳です。   米国国立標準技術研究所 (NIST) のサイバーセキュリティ フレームワークの最新版と、ネットワーク情報セキュリティ (NIS) 指令の導入に関する欧州ネットワーク情報セキュリティ庁 (ENISA) の提案の公開を受けて、私はふと一息ついて、これら 2 つの導入以降、 当社の重要なインフラストラクチャのセキュリティ保護の取り組みが進展してきたかどうかについて考えてみました。また、規制対象/影響下にある幅広いエコシステムから大きな支持を受けていたとしても、政治風土の違いがどれほど政策の結果に影響を及ぼすかということにも衝撃を受けました。   この 2 大経済圏の出発点は非常に似ていました。欧州の NIS 指令も米国の NIST フレームワークも、重要なインフラストラクチャのサイバーセキュリティの向上を目指すものです。これらは2013 年初め、ほぼ同時期に登場しました。まず、欧州委員会が NIS 指令を導入し、オバマ前米大統領がサイバーセキュリティ フレームワークの設立を目指すためのプロセスを定めた大統領命令に署名したのです。 米国と EU の政治、法律、執行をつかさどる各「機関」の大きな違いを考えれば、出発点が同じでも、両者がまったく異なる道を進んだことに何ら驚きはありません。現在、NIST フレームワークは、脅威の変化と世界中の導入者の経験に基づき、3…


Using Google OAuth 2.0 authorization server in Azure API Management

While trying out API Management’s in-preview SOAP to REST capabilities against Google’s AdWords API, I needed to enable Google’s OAuth 2.0 authorization in APIM to connect to the API. While each separately has good documentations and samples, I didn’t find the intersect of someone putting together to two. So here it is, how to use Google…


PIX 1707.25 – counter rollup, new Dr. PIX experiments, pixel kill reason, and pixtool.exe

Today we released PIX 1707.25 beta. New in this release: GPU counter improvements GPU counter values are now accurately rolled up from individual draws to their parent regions Added support for some AMD R5xx GPUs that did not previously work with PIX Improved accuracy of the crop__sol_pct and zrop__sol_pct counters on NVIDIA GPUs Dr. PIX…


Workflow Manager 1.0 Now Supported on Windows Server 2016 with CU4

We have completed our validation work and are pleased to announce that Workflow Manager Server 1.0 now supports the following platforms when used in a SharePoint Server 2016 environment: .NET 4.6+ (when using Service Bus Server 1.1 with KB3086798) Windows Server 2016 Windows 10 x64 (for development purposes) SQL Server 2014 & SQL Server 2016 To…


Workflow Manager 1.0 Cumulative Update 4 (WFM CU4) is now available on the Microsoft Download Center

Workflow Manager 1.0 Cumulative Update 4 (WFM CU4) is now available on the Microsoft Download Center. WFM CU4 contains fixes for Workflow Manager 1.0 (server) and Workflow Manager Client 1.0. WFM client CU4 is backward compatible with WFM servers 1.0, CU1, CU2, Refresh and CU3. WFM CU4 (server) is compatible with ServiceBus 1.0 CU1 and…


Introducing the Power BI solution template for Credit and Collections

Today we are excited to announce the Power BI solution template for Dynamics 365 Finance and Operations for Credit and Collections analytics. Purpose of this blog post is to explain who should use this solution template any why should they use it. Before we start, see this video for a quick tour. You probably know…


Understanding states in Release Management

Trying to code against release management APIs? This post will try to demystify the various states that are present in the release object and explain what each of them signify. First, we need to understand the structure of the release object. The release object is a wrapper to a bunch of artifacts and environments. Each…


Connecting to TFS 2017 using VS 2008/MSSCCI Provider for 2013.

As many organizations are upgrading to TFS 2017, there is a growing concern for version controlling old legacy projects on VS 2005/2008, and some confusion on steps to connect to Version Control of TFS 2017 using older Visual Studio (2005/2008) using the MSSCCI provider. This article aims to give steps to connect to TFS 2015/2017 using…


Best Practices for Azure SQL DataSync 2.0 tasks

The Azure SQL DataSync workflow is carried by different tasks at different stages. The first task is to provision destination databases (Initial Synchronization). Then data changes (update/insert/delete) are propagated to the destination by sync tasks. If any changes are made in dataset or schema, re-provisioning occurs. Deprovisioning is engaged when a database is removed from…