developers.de

How to create and publish nuget symbol packages

Holger Vetter — Fri, 27 Oct 2017 09:39:12 GMT

Creating a nuget package with symbols is quite easy.

You have 2 possible methods to create a nuget package with symbols:

From nuspec file. How to create nuspec file.
```
nuget pack MyPackage.nuspec -Symbols
```
From project file.
```
nuget pack MyProject.csproj -Symbols
```

Both of the commands will create 2 files {identifier}.symbols.nupkg and {identifier}.nupkg.

Publishing the nuget package

Normally I upload nuget package by just using drag&drop on the nuget upload page. This doesn't work with symbol packages, because you have 2 packages in the folder.

To publish symbol and normal package, you must use the nuget cli.

Get and set your Nuget API key.
Create both (normal + symbol) package. See the 2 possible options above.
Run nuget push {identifier}.nupkg -Source https://www.nuget.org/api/v2/package.
This will upload the {identifier}.nupkg to nuget and {identifier}.symbols.nupkgto the symbol server.

If the uploads were successful, result should look like this:

Part 2 of this tutorial will show how to use the symbol package to debug trough third party code.

Sources:
https://docs.microsoft.com/en-us/nuget/create-packages/symbol-packages
https://docs.microsoft.com/en-us/nuget/create-packages/publish-a-package

Load Balancing on Azure

Damir Dobric — Tue, 24 Oct 2017 05:57:00 GMT

Microsoft Azure support two different kind of Load Balancer configurations. For all internet traffic coming from outside into the Azure you will have to use so called “Internet Facing Load balancer”.

All traffic between virtual machines hosted in azure is controlled by “Internal Load balancer”. Currently, there are 3 Load Balancers in Azure:

- Azure Load Balancer
- Application Gateway
- Traffic Manager

Azure Load Balancer

This kind of load balancer supports internet-facing LB and internal LB. It is implemented at Layer 4 and supports any application protocol. It is usually used in conjunction with Azure VNets.

IF-LB uses so called hash-based distribution algorithm to distribute incoming public traffic as shown at the picture below:

The picture shows that traffic is distributed from publish source to internal (in Azure) destination, but it doesn’t describe how.

This LB supports two different algorithms to distribute the traffic. They are also called distribution modes.
Currently are supported two distribution modes:

- Hash Based Distribution Mode
- IP Affinity Distribution Mode

Hash Based Distribution Mode

It uses (by default) a hash composed over 5 variables:

- Source IP
- Source Port
- Destination IP
- Destination port
- Protocol type

IP Affinity Distribution Mode

IP Affinity mode sticks the session from source to destination. If can be configured to use Source-UP and Destination-IP to set the sticky session. Once the session is established, LB makes sure that all traffic is routed to the same destination.

In some scenarios affinity mode can be set to use also port number as 3th parameter for affinity session.

Application Gateway

Application Gateway is a service, which represents so called Application Delivery Controller as a service. It is a gateway with bunch of features in front of some application, which is running behind some dedicated IP address. Because it acts in front of application, it supports various load-balancing features at application level 7. Note that Azure Load balancer is working on lower-level 4.

Application Gateway supports round robin distribution, cookie-based session affinity, URL path-based routing, and the ability to host multiple websites behind a single gateway endpoint.

From the architecture point of view, gateway looks same as LB (se previous picture).

But note, that is is running on higher level. Incoming traffic is now HTTP/S and not some proprietary TCP or UDP protocol. Application Gateway is used for load balancing of HTTP, HTTP/S and WebSocket traffic. Because gateway knows everything about application protocols it can provide protocol dedicated features. For example,, this can be SSL offloading (SSL decryption and termination, then routing to application) or URL-based routing.
Such features are not supported by Load Balancer.

It is also remarkable that gateway can set policy for using of dedicated CipherSuite.

More over it provides Web Application Firewall as integrative part. Such firewalls protect an application from set of different vulnerabilities defined by OWASP rules. Some of rules are: SQL Injection , Cross Site Scripting , HTTP Protocol Violations and many others.

For more information about Application Gateway take a look here.

Traffic Manager

Unlike to Load Balancer and Application Gateway, Traffic Manager uses DNS *Domain Name System) to direct requests. Requests can be directed to various endpoints like VMs, WebApps, Cloud Services or some external services (from Azure point of view). Following picture shows how Traffic Manager looks up the DNS in request and chose some of destination endpoints based on set of routing method rules.

Core of Traffic Manager is Distribution of traffic according to one of traffic routing methods. For example, if you want to route all your traffic to a single endpoint, but you want to provide a failover endpoint, you will use so called priority routing. If you have 3 destinations, priority routing will chose the destination with highest priority as long it is online. If Primary fails, then next would be Node A, because priority 2 is higher than 3.

If you want to evenly distribute traffic, you will use weighted routing. In following example traffic will ve evenly distributed to Nodes A and B.

If your application is installed on different locations some kind of performance-based routing measured by DNS queries might be useful.

Traffic Manager looks up the source IP address of the incoming DNS request in the Internet Latency Table. Traffic Manager chooses an available endpoint in the Azure datacenter that has the lowest latency for that IP address range, then returns that endpoint in the DNS response.

Last, but not leas, you can use routing dependent on geographic region. Depending on from where request do come from, you can chose dedicated endpoints.

For more information about Traffic Manager take a look here.

Kill a process in Windows by Port Number

Indraneel Pole — Wed, 18 Oct 2017 09:20:44 GMT

While working with Angular projects, a lot of times I forget to kill the running NPM process before closing the command line tool. And then when I want to run the app on same port again it throws me an error that the port is used by some other process. Now, this is just an example, but it is quite possible that this might have happened with you as well while working on some web project. In case you are scratching your head for which command to use to kill the process just by knowing the port number, here is the post that might help you. Well I know this is not that great a problem, but sometimes we spend hours solving the dumbest problems.

So first you need to find the PID of your process that is running on that specific port. Here is the command that gives you list of all process with port numbers. Shoot this command in command prompt.

“netstat -a -o –n”

It will show you a similar output -

Now type Ctl + F to find the port that you are looking for. For me, it was 4200. Note the PID of this process in the last column. For me it was 15508

Now simply use the command to kill the process by PID -

“taskkill /F /PID 15508”

Make sure to change the PID to your own PID. And that is it. You can run the new process on same port now.

NullReferenceException with more informations (Propertyname)

Holger Vetter — Tue, 17 Oct 2017 08:44:30 GMT

Hey,

this week I saw this exception in Visual Studio 2017 (15.3.5):

I was wondering when VS got the feature to display the property(getter) which caused the exception.

Think the feature is new to VS. If anybody knows when this feature was added to VS, please comment below. :)

AGENDA .NETConf in Frankfurt Oct.2017

Damir Dobric — Thu, 12 Oct 2017 09:54:11 GMT

Covered Topics:

.NET Core Intro

Frameworks and Runtime

Creating .NET Core Framework Dependent Applications

Creating .NET Core Self Contained Applications

.NET Core and Docker

Creating UI with .NET Core

.NET Foundation

.NET Standard and runtimes

Machine Learning with .NET Core

HoloLens, Unity3D, and .NET – a Mixed Reality with sprinkles of .NET Core

Cannot install .NET Core on Ubuntu?

Damir Dobric — Mon, 09 Oct 2017 05:33:00 GMT

When trying to install .NET Core on Ubuntu as described here, with following command:

sudo sh -c 'echo "deb [arch=amd64] https://packages.microsoft.com/repos/microsoft-ubuntu-xenial-prod xenial main" > /etc/apt/sources.list.d/dotnetdev.list'

you might get following error:

Failed to fetch https://packages.microsoft.com/repos/microsoft-ubuntu-xenial-prod/dists/xenial/InRelease

To workaround this issue register feed through HTTP instead of HTTS:

sudo sh -c 'echo "deb [arch=amd64] http://packages.microsoft.com/repos/microsoft-ubuntu-xenial-prod xenial main" > /etc/apt/sources.list.d/dotnetdev.list'

.NET Core Deep Dive

Damir Dobric — Sat, 07 Oct 2017 09:30:18 GMT

Microsoft .NET Conf is partnering with Azure Meetup Frankfurt and will organize around the globe many local in-person events between September 19 through the end of October!

For more information please refer here.

You can join us to learn more about .NET and the new .NET Core 2.0 release.

We will start at Oct.12 at 4pm and end as usual around 8pm.

Content will be delivered by:

- Andreas Erben (Mixed Reality Architect, MVP)

- Andreas Lehmann (Cloud Solution Architect - daenet GmbH)

- Mofaggol Hoshen (University of Applied Sciences Frankfurt am Main)

- Sebastian Valero-Graefe (DevOp - daenet GmbH)

- Jon Galloway (.NET Foundation executive director )

- Damir Dobric (MVP, RD https://about.me/damirdobric )

Jon Galloway .NET Foundation executive director will join us via Skype and talk about .NET Momentum.

Hope to see you there. We will have some food and drinks and lot of goodies sent from Redmond (T-Shirts, stickers, etc.. :)

AGENDA

1. .NET Core as Cloud Dev Framework: Why and What?

2. .NET Standard and runtimes

3. Creating .NET Core Framework Dependent Applications

4. Creating .NET Core Self Contained Applications

5. Deploying and running .NET Core on different operative systems

6. Creating UI with .NET Core

7. .NET Core and Containers

8. Testing .NET Core Applications

9. HoloLens, Unity3D, and .NET – a Mixed Reality with sprinkles of .NET Core

10. Machine Learning with .NET Core

Come together / Dinner

Please note that you have to provide your valid ID at registration desk at e-Shelter. Usually if all attendees arrive just few minutes before event, registration might take 15-30 minutes. Please be on time at e-shelter facility.

.NET Core: 'Publish' target is not supported

Damir Dobric — Tue, 19 Sep 2017 04:35:00 GMT

When you are building Self Contained Deployments, sometimes the publish process cannot resolve the target framework. For example:

dotnet publish -r win10-x64

dotnet publish -r win10-x64 --self-contained

In this case you will get following error:

Error :
The 'Publish' target is not supported without specifying a target framework.
The current project targets multiple frameworks, please specify the framework for the published application.

To workaround this error, you have to explicitly specify the target framework.

dotnet publish -r win10-x64 --self-contained -f netcoreapp2.0

.NET Cross-Framework referencing

Damir Dobric — Sun, 17 Sep 2017 15:24:48 GMT

Assume, there is a .NET Framework application called NetDesktopApp and .NET Core library NetCoreLib2.
Further, NetCoreDesktopApp references NetCoreLib2.
Implementation of NetCoreLib2 looks like:

using System;

namespace NetCoreLib2
{
    public class MyNetCoreLib2
    {
        public static string Go(long a)
        {
            return a++.ToString();
        }
    }
}

Implementation of NetCoreDesktopApp looks like:

namespace NetDesktopApp
{
    class Program
    {
         static void Main(string[] args)
        {
            Console.WriteLine(MyNetCoreLib2.Go(DateTime.Now.Ticks));
         }
    }

When a .NET application starts, then following libraries are loaded.

Please note assembly netstandard.dll. This assembly is implicitly injected in the project by Visual Studio, when .NET Core assembly is referenced. The purpose of that assembly is to do type forwarding.

.NET Framework Application

Before .NET Core, thinks looked simpler. Typical .NET Framework minimal application loads following assemblies if no .NET Core libraries are referenced.

As you see, only two assemblies are loaded. Your application and runtime assembly. If you take a look on such project in VS, you will notice much more assemblies. However they are not loaded if not used.

.NET Core Application

Now, let’s take a look what happen if .NET Core application is loaded. In this case no mscorelib.dll is loaded, because it is not a part of .NET Core. But note, this time System.Runtime.Dll is loaded.

.NET Core Application with reference to .NET Standard library

In this case, I have same .NET Core application, which this time references a .NET Standard library. When started .NET Core application will load one additional assembly StandardLibrary.dll.

.NET Core Application with reference to .NET Standard library, which references .NET Framework assembly

In this example, I have created .NET Core application (NetCoreApp), which references .NET Core Library (NetCoreLib), which finally references a .NET Framework library (NetDesktopLib2). There is also .NET Framework Library (NetDesktopLib), which is referenced from application too.

In this case, System.Rrntime is loaded from .NET Core and also mscorelib from .NET Framework.

ASP.NET Core Issue: HTTP Error 502.5

Damir Dobric — Thu, 14 Sep 2017 09:27:53 GMT

If you are deploying ASP.NET core 2.0 application to Azure App Service you might get following error:

HTTP Error 502.5 - Process Failure

Common causes of this issue:

The application process failed to start
The application process started but then stopped
The application process started but failed to listen on the configured port

As usual, first of all you have to do is don’t read the error message. The problem is that your AppService container already contains a version of .NET Core v1.* (or something else), which has deployed assemblies, which disturbs new deployment.

Right now, this issue is related to migration from .NET Core 1 to .NET Core 2. But similar problem might happen in the future, due to some other reason.

The solution for this problem is to delete the exisiting deployment manually. You might do this by connecting via FTP or by using of Kudu.

If you want to connect to Kudu type following URL: https://YOURSERVICENAME.scm.azurewebsites.de/DebugConsole

After successfull connect, you will see following:

Then you can enter “dir” command to see the content of the root.

As next, navigate to following folder

D:\home\site\wwwroot>

No you can delete all files with following command:

del *.*

After that you can deploy solution again.

Raspberry Pi Windows 10 IoT Core - How to find isolated storage of your application?

Indraneel Pole — Thu, 14 Sep 2017 07:04:07 GMT

While working on IoT projects, if you are using Windows 10 IoT Core, things can be really painful sometimes. There are advantages and disadvantages of using Windows 10IoT Core. Advantage being you can apply most of your Windows knowledge in some way to Windows 10 IoT Core. The bad thing a lot of times it is the same but the different and that confusion makes your life hell. It recently happened with me when I used Isolated Storage on Raspberry Pi in my project and it took me 2 hours to find the path of it. So if anybody is wondering with the same question, here is where it lies.

The isolated storage lies inside Package folder of your app. Every app that is installed on Windows OS creates an app package. On normal Windows machines, your app packages are installed at C drive at your user account inside AppData\Local. The Path looks something like -

C:\Users\XYZ\AppData\Local\Packages

And inside this lies your package inside which you can access the isolated storage files.

On Windows 10 IoT Core however you have two “Users” folders, one is directly on the root level and another is inside the Data folder. If you try to find inside Users folder you still go to packages folder, but you will not find anything in there. To go to app packages you have to go inside Data\Users folder and then select “DefaultAccount” which is a hidden folder. This DefaultAccount then has a similar path as of Windows machine. The path looks like this -

\\IP_Address_Of_Your_Machine\c$\Data\Users\DefaultAccount\AppData\Local\Packages\20c45e87-953a-4d99-919b-c6ee7e9642d3_h95tnwbrnsgam\LocalState\

The GUID inside packages folder is your app folder and inside local state you can access isolated storage.

I hope it helps

How about ‘mscorelib’ reference?

Damir Dobric — Fri, 25 Aug 2017 05:33:00 GMT

Sometimes, it is very difficult to understand what happen behind build process inside of complex solutions. You think you did all correct, and then you write simple line of, which is basically doing ‘nothing’ and then:

“You must add a reference to assembly mscorlib, version=4.0.0”

It means you miss everything in framework. The problem is that you probably are targeting multiple frameworks. For example, I have a project with following targets:

<TargetFrameworks>netstandard1.3;net46</TargetFrameworks>

The error shown above is related to netstandard1.3. To fix this, you cannot simply go to project references and add reference to mscorelib.

Rather, you should add a reference to following package:

Microsoft.NETCore.Portable.Compatibility

That will make your project compliable.

Microsoft.IdentityModel.Tokens.SecurityTokenSignatureKeyNotFoundException

Damir Dobric — Wed, 23 Aug 2017 14:38:23 GMT

I guess, when you see error shown below (or similar) error, you might get kind of crazy:

Microsoft.IdentityModel.Tokens.SecurityTokenSignatureKeyNotFoundException: 'IDX10501: Signature validation failed. Unable to match 'kid': 'VWVIc1WD1Tksbb301sasM5kOq5Q',
token: '{"alg":"RS256","typ":"JWT","x5t"

This error means that signature of the specified token cannot be validated. This happens if your token is issued by for example AAD in public cloud and you are validating signature against another cloud like german-cloud.

In another words, the client has obtained the token from Authority1 and Service is validating signature by Authority2.

AAD endpoint in configuration client and service must match.

Unable to resolve service type while injecting dependencies

Damir Dobric — Tue, 15 Aug 2017 15:23:32 GMT

When implementing .NET Core dependency injection inside of ASP.NET Core or .NET Core. Assume you have implemented some class like 'IoTService.Config.GatewayConfig' and get following error on startup:

{"message":"Unable to resolve service for type 'IoTService.Config.GatewayConfig' while attempting to activate 'IoTService.GatewayHelper'.","type":"InvalidOperationException"}

This is how I have initialized injection:

services.Configure<GatewayConfig>(Configuration.GetSection("IotHubMap"));
services.AddScoped<IGatewayHelper, GatewayHelper>();

The error shown above will be thrown if the constructor shown in yellow is not implemented. Internal implementation is always looking for IOptions. The code shown below demonstrate hot to workaround this error and how to implement injectable class out of ASP.NET and need to implement IOptions interface.

public class GatewayHelper : ISOmething
{
private GatewayConfig m_Cfg;

public GatewayHelper(IOptions<GatewayConfig> options) : this(options.Value)
{

}

        public GatewayHelper(GatewayConfig cfg)
         {
            this.m_Cfg = cfg;
        }

How to find out Callback URI of the Windows 10 App?

Damir Dobric — Mon, 14 Aug 2017 05:20:00 GMT

Usually, when implementing AAD authentication in application, according to OAuth protocol, you will have to provide so called Callback-URI. This is the URL of the endpoint capable of receiving redirected request from authority. Because the specification as originally written for web applications, this kind of URL is not natural for native apps.

Depending on type of operative system or even better, depending on client library, which you use, this URL might look different. In a case of UWP (Universal Windows Application), the URL can be extracte as follows:

string URI = string.Format("ms-appx-web://Microsoft.AAD.BrokerPlugIn/{0}", WebAuthenticationBroker.GetCurrentApplicationCallbackUri().Host.ToUpper());

As a result you will get something like this:

ms-appx-web://Microsoft.AAD.BrokerPlugIn/S-1-XX-2-00000000-11111-22222-4444-2290055178-222222-1111111

This URL is what you have to set in application blade in Azure AAD portal.

What is behind ‘404-error’ in Azure AD B2C?

Damir Dobric — Mon, 07 Aug 2017 05:35:00 GMT

AAD B2C is definitely an interesting approach to simplify dealing with various cloud identities. However, we should not forget, that working with security is always complex and can be very wired. In this post I will describe one example.

Let’s assume, we want to perform a sign in operation from some application. In my case this is WPF application. It means it is running on Windows in .NET Desktop framework.

To sign-in, I use following code, which use MSAL API:

var authResult = await App.PublicClientApp.AcquireTokenAsync(App.ApiScopes, GetUserByPolicy(App.PublicClientApp.Users, “BLABLA”), UIBehavior.SelectAccount, string.Empty, null, App.Authority);

This code will fail with following error, because the policy “BLABLA” does not exist.

System.Runtime.Serialization.SerializationException: There was an error deserializing the object of type Microsoft.Identity.Client.Internal.OAuth2.TokenResponse. Encountered unexpected character '<'. ---> System.Xml.XmlException: Encountered unexpected character '<'.

If you trace HTTP traffic, you will find more information behind this error:

<h2>404 - File or directory not found.</h2>
<h3>The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable.</h3>

This means, that error 404 will happen if you specify the policy which does not exist, at least.

DesktopAppConverter error : qualified file name must be less than 260

Damir Dobric — Sat, 22 Jul 2017 12:53:00 GMT

When working with Desktop Converter, you might get following error:

C:\Program Files\WindowsApps\Microsoft.DesktopAppConverter_2.0.2.0_x64__8wekyb3d8bbwe\DesktopAppConverter.ps1 : The
specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and
the directory name must be less than 248 characters.
At line:1 char:1
+ &'C:\Program Files\WindowsApps\Microsoft.DesktopAppConverter_2.0.2.0_ ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException
+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,DesktopAppConverter.ps1

This error has nothing to do with the length f any of your application files. The problem is destination argument of following command:

> DesktopAppConverter.exe -Installer C:\Temp\NodejsApp\NodejsApp -AppExecutable node.exe -Destinat
ion C:\Temp\NodejsApp\NodejsApp\packages -PackageName "MyNodeApp" -Publisher "CN=MyPublisher" -Version 0.0.0.1

This command creates the package from application in path ‘C:\Temp\NodejsApp\NodejsApp ’ and will try to store it to path C:\Temp\NodejsApp\NodejsApp\packages .

Because creating process will read specified path, but in the same time will create packages under the reading path, it will recursively grow until it crashes.

Solution is very easy. You should create a package out of application root:

DesktopAppConverter.exe -Installer C:\Temp\NodejsApp\NodejsApp -AppExecutable node.exe -Destinat
ion C:\Temp\NodejsApp\packages -PackageName "MyNodeApp" -Publisher "CN=MyPublisher" -Version 0.0.0.1

How to access log files on Windows IoT Core device?

Damir Dobric — Thu, 20 Jul 2017 09:36:50 GMT

Sometimes, when running on Windows IoT Core device, you might have some issues when trying to access files in LocalAppData folder.As you see there is no any file shown in dashboard. But, believe me, there are files in the folder.

Interestingly, when this happen, you will be able to access files via PowerShell. Following power-shell command shows how to fo that.

[192.168.0.123]:
cd C:\Data\Users\DefaultAccount\AppData\local\Packages\20c45e87-953a-4d99-919b-c6ee7e9642d3_h95tnwbrnsgam\LocalState

Configuring Application Configuration in ASP.NET Core 2

Damir Dobric — Sun, 16 Jul 2017 08:16:44 GMT

Configuration of asp.net core seems to be particularly moved from startup.cs in program.cs. Here is one example:

public class Program
    {
        public static void Main(string[] args)
        {
            BuildWebHost(args).Run();
        }

        public static IWebHost BuildWebHost(string[] args) =>
            WebHost.CreateDefaultBuilder(args)
            .ConfigureAppConfiguration((ctx, cfgBuilder) =>
            {
                cfgBuilder.
                 AddJsonFile("appsettings.json", optional: false, reloadOnChange: true)
                .AddJsonFile($"appsettings.{ctx.HostingEnvironment.EnvironmentName}.json",
                 optional: true)
                .AddEnvironmentVariables();
            })
                .UseStartup<Startup>()
                .Build();
    }

Swagger IncludeXmlComments PlatformServices (obsolete) replacement

Holger Vetter — Fri, 30 Jun 2017 09:31:13 GMT

We migrated a project to ASP.NET Core 2 (preview) and needed to configure swagger.

In ASP.NET Core v1 we used this code to load the auto generated xml file into swagger:

services.ConfigureSwaggerGen(options =>

{

//Determine base path for the application.

var basePath = PlatformServices.Default.Application.ApplicationBasePath;

//Set the comments path for the swagger json and ui.

options.IncludeXmlComments(System.IO.Path.Combine(basePath, "ProjectName.xml"));

});

Since PlatformServices is obsolete (https://github.com/aspnet/PlatformAbstractions), you shouldn't use this for your (new) projects anymore.
Like the github page states, you should use the equivalent .NET API instead.

Here is what I use instead of PlatFormAbstractions (PlatformServices) for loading the xml into swagger:

services.ConfigureSwaggerGen(options =>

{

//Determine base path for the application.

var basePath = AppContext.BaseDirectory;

var assemblyName = System.Reflection.Assembly.GetEntryAssembly().GetName().Name;

var fileName = System.IO.Path.GetFileName(assemblyName + ".xml");

//Set the comments path for the swagger json and ui.

options.IncludeXmlComments(System.IO.Path.Combine(basePath, fileName));

});

Hint: You could add a check here, if the file really exists before loading it.

How to deal with Assembly Version in .NET Core?

Damir Dobric — Tue, 27 Jun 2017 14:31:41 GMT

Most enterprise application soon or latter, have a requirement to trace out the version of a currently running application. This post shows few example, which demonstrates how to do this in .NET Core.

var ver = Assembly.GetEntryAssembly().GetCustomAttribute<AssemblyInformationalVersionAttribute>().InformationalVersion;

var attrs = typeof(Startup)
.GetTypeInfo()
.Assembly.GetCustomAttributes();

var runtimeVersion = typeof(Startup)

.GetTypeInfo()

.Assembly

.GetCustomAttribute<AssemblyFileVersionAttribute>();

var tokens = runtimeVersion.Version.Split('.');

m_Version = new Version(runtimeVersion.Version)

What is really supported in German Azure DCs?

Damir Dobric — Tue, 13 Jun 2017 08:36:00 GMT

Hosting of a Cloud is really, really complex task. Even keeping of documentation in sync with deployment of several resources is incredibly complicate. I stuck in many documents, roadmaps etc. And over and over again, by writing of software dedicated for some exclusive club DCs might be a challenge.

Just imagine you want to create or delete some resource. To do this, you will implicitly have to provide API version of the resource provider API. Usually the API is transparent for you, because you will (you should) typically use some SDK, which hides that from us. This is a nice simplification, but we are open source now. That means that SDK cannot follow the speed of shipping of resources as we learned it in a past. The high cadency is very innovative way of making things, but building of SDKs and writing of documentation become a new challenge of the century. That turns out, we will more often have to dig deep in the system to be sure to do a right thing.

For this reason I wrote a simple application, which dumps out all deployed resource providers in one hosting DC.
This post is a dump of all providers available in German DCs at time of writing of this post.

ProviderId:/subscriptions/1e498be8-9b44-43e5-8a7e-96e59ecbfe78/providers/Microsoft.Devices
Locations: Germany Central, Germany Northeast
ResourceType: checkNameAvailability
API: 2017-01-19, 2016-02-03, 2015-08-15-preview

Locations: Germany Central, Germany Northeast
ResourceType: operations
API: 2017-01-19, 2016-02-03, 2015-08-15-preview

Locations: Germany Central, Germany Northeast
ResourceType: IotHubs
API: 2017-01-19, 2016-02-03, 2015-08-15-preview

ProviderId:/subscriptions/1e498be8-9b44-43e5-8a7e-96e59ecbfe78/providers/Microsoft.DocumentDB
Locations: Germany Central, Germany Northeast
ResourceType: databaseAccounts
API: 2015-04-08, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: databaseAccountNames
API: 2015-04-08, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: operations
API: 2015-04-08, 2014-04-01

ProviderId:/subscriptions/1e498be8-9b44-43e5-8a7e-96e59ecbfe78/providers/Microsoft.EventHub
Locations: Germany Central, Germany Northeast
ResourceType: namespaces
API: 2015-08-01, 2014-09-01

Locations:
ResourceType: checkNamespaceAvailability
API: 2015-08-01, 2014-09-01

Locations:
ResourceType: checkNameAvailability
API: 2015-08-01, 2014-09-01

Locations:
ResourceType: sku
API: 2015-08-01, 2014-09-01

Locations:
ResourceType: operations
API: 2015-08-01, 2014-09-01

ProviderId:/subscriptions/1e498be8-9b44-43e5-8a7e-96e59ecbfe78/providers/microsoft.insights
Locations: Germany Northeast, Germany Central
ResourceType: alertrules
API: 2016-03-01, 2015-04-01, 2014-04-01

Locations: Germany Northeast, Germany Central
ResourceType: autoscalesettings
API: 2015-04-01, 2014-04-01

Locations:
ResourceType: eventtypes
API: 2017-03-01-preview, 2016-09-01-preview, 2015-04-01, 2014-11-01, 2014-04-01

Locations:
ResourceType: eventCategories
API: 2015-04-01

Locations: Global
ResourceType: actiongroups
API: 2017-04-01

Locations: Global
ResourceType: activityLogAlerts
API: 2017-04-01, 2017-03-01-preview

Locations: Germany Northeast, Germany Central
ResourceType: diagnosticSettings
API: 2017-05-01-preview, 2016-09-01, 2015-07-01

Locations: Germany Northeast, Germany Central
ResourceType: metricDefinitions
API: 2017-05-01-preview, 2016-03-01, 2015-07-01

Locations: Germany Northeast, Germany Central
ResourceType: logDefinitions
API: 2015-07-01

Locations:
ResourceType: logprofiles
API: 2016-03-01

Locations: Germany Northeast, Germany Central
ResourceType: metrics
API: 2017-05-01-preview, 2016-09-01, 2016-06-01

ProviderId:/subscriptions/1e498be8-9b44-43e5-8a7e-96e59ecbfe78/providers/Microsoft.Network
Locations: Germany Central, Germany Northeast
ResourceType: virtualNetworks
API: 2017-04-01, 2017-03-01, 2016-12-01, 2016-11-01, 2016-10-01, 2016-09-01, 2016-08-01, 2016-07-01, 2016-06-01, 2016-03-30, 2015-06-15, 2015-05-01-preview, 2014-12-01-preview

Locations: Germany Central, Germany Northeast
ResourceType: publicIPAddresses
API: 2017-04-01, 2017-03-01, 2016-12-01, 2016-11-01, 2016-10-01, 2016-09-01, 2016-08-01, 2016-07-01, 2016-06-01, 2016-03-30, 2015-06-15, 2015-05-01-preview, 2014-12-01-preview

Locations: Germany Central, Germany Northeast
ResourceType: networkInterfaces
API: 2017-04-01, 2017-03-01, 2016-12-01, 2016-11-01, 2016-10-01, 2016-09-01, 2016-08-01, 2016-07-01, 2016-06-01, 2016-03-30, 2015-06-15, 2015-05-01-preview, 2014-12-01-preview

Locations: Germany Central, Germany Northeast
ResourceType: loadBalancers
API: 2017-04-01, 2017-03-01, 2016-12-01, 2016-11-01, 2016-10-01, 2016-09-01, 2016-08-01, 2016-07-01, 2016-06-01, 2016-03-30, 2015-06-15, 2015-05-01-preview, 2014-12-01-preview

Locations: Germany Central, Germany Northeast
ResourceType: networkSecurityGroups
API: 2017-04-01, 2017-03-01, 2016-12-01, 2016-11-01, 2016-10-01, 2016-09-01, 2016-08-01, 2016-07-01, 2016-06-01, 2016-03-30, 2015-06-15, 2015-05-01-preview, 2014-12-01-preview

Locations: Germany Central, Germany Northeast
ResourceType: routeTables
API: 2017-04-01, 2017-03-01, 2016-12-01, 2016-11-01, 2016-10-01, 2016-09-01, 2016-08-01, 2016-07-01, 2016-06-01, 2016-03-30, 2015-06-15, 2015-05-01-preview, 2014-12-01-preview

Locations: Germany Central, Germany Northeast
ResourceType: virtualNetworkGateways
API: 2017-04-01, 2017-03-01, 2016-12-01, 2016-11-01, 2016-10-01, 2016-09-01, 2016-08-01, 2016-07-01, 2016-06-01, 2016-03-30, 2015-06-15, 2015-05-01-preview, 2014-12-01-preview

Locations: Germany Central, Germany Northeast
ResourceType: localNetworkGateways
API: 2017-04-01, 2017-03-01, 2016-12-01, 2016-11-01, 2016-10-01, 2016-09-01, 2016-08-01, 2016-07-01, 2016-06-01, 2016-03-30, 2015-06-15, 2015-05-01-preview, 2014-12-01-preview

Locations: Germany Central, Germany Northeast
ResourceType: connections
API: 2017-04-01, 2017-03-01, 2016-12-01, 2016-11-01, 2016-10-01, 2016-09-01, 2016-08-01, 2016-07-01, 2016-06-01, 2016-03-30, 2015-06-15, 2015-05-01-preview, 2014-12-01-preview

Locations: Germany Central, Germany Northeast
ResourceType: applicationGateways
API: 2017-04-01, 2017-03-01, 2016-12-01, 2016-11-01, 2016-10-01, 2016-09-01, 2016-08-01, 2016-07-01, 2016-06-01, 2016-03-30, 2015-06-15, 2015-05-01-preview, 2014-12-01-preview

Locations:
ResourceType: locations
API: 2017-04-01, 2017-03-01, 2016-12-01, 2016-11-01, 2016-10-01, 2016-09-01, 2016-08-01, 2016-07-01, 2016-06-01, 2016-03-30, 2015-06-15, 2015-05-01-preview, 2014-12-01-preview

Locations:
ResourceType: locations/operations
API: 2017-04-01, 2017-03-01, 2016-12-01, 2016-11-01, 2016-10-01, 2016-09-01, 2016-08-01, 2016-07-01, 2016-06-01, 2016-03-30, 2015-06-15, 2015-05-01-preview, 2014-12-01-preview

Locations:
ResourceType: locations/operationResults
API: 2017-04-01, 2017-03-01, 2016-12-01, 2016-11-01, 2016-10-01, 2016-09-01, 2016-08-01, 2016-07-01, 2016-06-01, 2016-03-30, 2015-06-15, 2015-05-01-preview, 2014-12-01-preview

Locations: Germany Central, Germany Northeast
ResourceType: locations/CheckDnsNameAvailability
API: 2017-04-01, 2017-03-01, 2016-12-01, 2016-11-01, 2016-10-01, 2016-09-01, 2016-08-01, 2016-07-01, 2016-06-01, 2016-03-30, 2015-06-15, 2015-05-01-preview, 2014-12-01-preview

Locations: Germany Central, Germany Northeast
ResourceType: locations/usages
API: 2017-04-01, 2017-03-01, 2016-12-01, 2016-11-01, 2016-10-01, 2016-09-01, 2016-08-01, 2016-07-01, 2016-06-01, 2016-03-30, 2015-06-15, 2015-05-01-preview, 2014-12-01-preview

Locations:
ResourceType: operations
API: 2017-04-01, 2017-03-01, 2016-12-01, 2016-11-01, 2016-10-01, 2016-09-01, 2016-08-01, 2016-07-01, 2016-06-01, 2016-03-30, 2015-06-15, 2015-05-01-preview, 2014-12-01-preview

Locations: Germany Central, Germany Northeast
ResourceType: routeFilters
API: 2017-04-01, 2017-03-01, 2016-12-01

Locations: Germany Central, Germany Northeast
ResourceType: expressRouteCircuits
API: 2017-04-01, 2017-03-01, 2016-12-01, 2016-11-01, 2016-10-01, 2016-09-01, 2016-08-01, 2016-07-01, 2016-06-01, 2016-03-30, 2015-06-15, 2015-05-01-preview, 2014-12-01-preview

Locations:
ResourceType: expressRouteServiceProviders
API: 2017-04-01, 2017-03-01, 2016-12-01, 2016-11-01, 2016-10-01, 2016-09-01, 2016-08-01, 2016-07-01, 2016-06-01, 2016-03-30, 2015-06-15, 2015-05-01-preview, 2014-12-01-preview

Locations:
ResourceType: bgpServiceCommunities
API: 2017-04-01, 2017-03-01, 2016-12-01

Locations:
ResourceType: applicationGatewayAvailableWafRuleSets
API: 2017-04-01, 2017-03-01

Locations: global
ResourceType: trafficmanagerprofiles
API: 2017-05-01, 2017-03-01, 2015-11-01

Locations: global
ResourceType: checkTrafficManagerNameAvailability
API: 2017-05-01, 2017-03-01, 2015-11-01

Locations: global
ResourceType: trafficManagerGeographicHierarchies
API: 2017-05-01, 2017-03-01

Locations:
ResourceType: serviceTunnelServices
API: 2017-04-01

ProviderId:/subscriptions/1e498be8-9b44-43e5-8a7e-96e59ecbfe78/providers/Microsoft.ServiceBus
Locations: Germany Central, Germany Northeast
ResourceType: namespaces
API: 2015-08-01, 2014-09-01

Locations:
ResourceType: checkNamespaceAvailability
API: 2015-08-01, 2014-09-01

Locations:
ResourceType: checkNameAvailability
API: 2015-08-01, 2014-09-01

Locations:
ResourceType: premiumMessagingRegions
API: 2015-08-01, 2014-09-01

Locations:
ResourceType: sku
API: 2015-08-01, 2014-09-01

Locations:
ResourceType: operations
API: 2015-08-01, 2014-09-01

ProviderId:/subscriptions/1e498be8-9b44-43e5-8a7e-96e59ecbfe78/providers/Microsoft.Sql
Locations: Germany Central, Germany Northeast
ResourceType: operations
API: 2014-04-01-preview, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: locations
API: 2014-04-01-preview, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: locations/capabilities
API: 2014-04-01-preview, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: locations/usages
API: 2014-04-01-preview

Locations: Germany Central, Germany Northeast
ResourceType: checkNameAvailability
API: 2014-04-01-preview, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: servers
API: 2014-04-01-preview, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: servers/databases
API: 2015-05-01-preview, 2014-04-01-preview, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: servers/serviceObjectives
API: 2014-04-01-preview, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: servers/communicationLinks
API: 2014-04-01-preview, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: servers/administrators
API: 2014-04-01-preview, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: servers/administratorOperationResults
API: 2014-04-01-preview, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: servers/restorableDroppedDatabases
API: 2014-04-01-preview, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: servers/recoverableDatabases
API: 2014-04-01-preview, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: servers/import
API: 2014-04-01-preview, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: servers/importExportOperationResults
API: 2014-04-01-preview, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: servers/operationResults
API: 2014-04-01-preview, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: servers/firewallrules
API: 2014-04-01-preview, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: servers/databaseSecurityPolicies
API: 2014-04-01-preview, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: servers/auditingPolicies
API: 2014-04-01-preview, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: servers/recommendedElasticPools
API: 2014-04-01-preview, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: servers/databases/auditingPolicies
API: 2014-04-01-preview, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: servers/databases/connectionPolicies
API: 2014-04-01-preview, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: servers/connectionPolicies
API: 2014-04-01-preview, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: servers/databases/dataMaskingPolicies
API: 2014-04-01-preview, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: servers/databases/dataMaskingPolicies/rules
API: 2014-04-01-preview, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: servers/databases/securityAlertPolicies
API: 2014-04-01-preview, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: servers/securityAlertPolicies
API: 2015-05-01-preview

Locations: Germany Central, Germany Northeast
ResourceType: servers/databases/auditingSettings
API: 2015-05-01-preview

Locations: Germany Central, Germany Northeast
ResourceType: servers/auditingSettings
API: 2015-05-01-preview

Locations: Germany Central, Germany Northeast
ResourceType: servers/elasticpools
API: 2014-04-01-preview, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: servers/failoverGroups
API: 2015-05-01-preview

Locations: Germany Central, Germany Northeast
ResourceType: locations/failoverGroupAzureAsyncOperation
API: 2015-05-01-preview

Locations: Germany Central, Germany Northeast
ResourceType: locations/failoverGroupOperationResults
API: 2015-05-01-preview

Locations: Germany Central, Germany Northeast
ResourceType: servers/usages
API: 2014-04-01-preview, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: servers/databases/metricDefinitions
API: 2014-04-01-preview, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: servers/databases/metrics
API: 2014-04-01-preview, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: servers/elasticpools/metrics
API: 2014-04-01-preview, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: servers/elasticpools/metricdefinitions
API: 2014-04-01-preview, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: servers/databases/topQueries
API: 2014-04-01-preview, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: servers/databases/topQueries/queryText
API: 2014-04-01-preview, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: servers/advisors
API: 2015-05-01-preview, 2014-04-01-preview, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: servers/elasticPools/advisors
API: 2015-05-01-preview, 2014-04-01-preview, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: servers/databases/advisors
API: 2015-05-01-preview, 2014-04-01-preview, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: servers/elasticPoolEstimates
API: 2015-05-01-preview

Locations: Germany Central, Germany Northeast
ResourceType: servers/databases/auditRecords
API: 2015-05-01-preview

ProviderId:/subscriptions/1e498be8-9b44-43e5-8a7e-96e59ecbfe78/providers/Microsoft.Storage
Locations: Germany Central, Germany Northeast
ResourceType: storageAccounts
API: 2017-06-01, 2016-12-01, 2016-05-01, 2016-01-01, 2015-06-15, 2015-05-01-preview

Locations:
ResourceType: storageAccounts/listAccountSas
API: 2017-06-01, 2016-12-01, 2016-05-01

Locations:
ResourceType: operations
API: 2017-06-01, 2016-12-01, 2016-05-01, 2016-01-01, 2015-06-15, 2015-05-01-preview

Locations:
ResourceType: usages
API: 2017-06-01, 2016-12-01, 2016-05-01, 2016-01-01, 2015-06-15, 2015-05-01-preview

Locations:
ResourceType: checkNameAvailability
API: 2017-06-01, 2016-12-01, 2016-05-01, 2016-01-01, 2015-06-15, 2015-05-01-preview

ProviderId:/subscriptions/1e498be8-9b44-43e5-8a7e-96e59ecbfe78/providers/Microsoft.StreamAnalytics
Locations: Germany Central, Germany Northeast
ResourceType: streamingjobs
API: 2017-04-01-preview, 2016-03-01, 2015-11-01, 2015-10-01, 2015-09-01, 2015-08-01-preview, 2015-06-01, 2015-05-01, 2015-04-01, 2015-03-01-preview

Locations: Germany Central, Germany Northeast
ResourceType: locations
API: 2017-04-01-preview, 2016-03-01, 2015-11-01, 2015-10-01, 2015-09-01, 2015-08-01-preview, 2015-06-01, 2015-05-01, 2015-04-01, 2015-03-01-preview

Locations:
ResourceType: locations/quotas
API: 2017-04-01-preview, 2016-03-01, 2015-11-01, 2015-10-01, 2015-09-01, 2015-08-01-preview, 2015-06-01, 2015-05-01, 2015-04-01, 2015-03-01-preview

Locations: Germany Central, Germany Northeast
ResourceType: operations
API: 2017-04-01-preview, 2016-03-01, 2015-11-01, 2015-10-01, 2015-09-01, 2015-08-01-preview, 2015-06-01, 2015-05-01, 2015-04-01, 2014-04-01

ProviderId:/subscriptions/1e498be8-9b44-43e5-8a7e-96e59ecbfe78/providers/Microsoft.Web
Locations: Germany Central, Germany Northeast
ResourceType: sites/extensions
API: 2016-08-01, 2016-03-01, 2015-08-01, 2015-07-01, 2015-06-01, 2015-05-01, 2015-04-01, 2015-02-01, 2014-11-01, 2014-06-01, 2014-04-01-preview, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: sites/slots/extensions
API: 2016-08-01, 2016-03-01, 2015-08-01, 2015-07-01, 2015-06-01, 2015-05-01, 2015-04-01, 2015-02-01, 2014-11-01, 2014-06-01, 2014-04-01-preview, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: sites/instances
API: 2016-08-01, 2016-03-01, 2015-08-01, 2015-07-01, 2015-06-01, 2015-05-01, 2015-04-01, 2015-02-01, 2014-11-01, 2014-06-01, 2014-04-01-preview, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: sites/slots/instances
API: 2016-08-01, 2016-03-01, 2015-08-01, 2015-07-01, 2015-06-01, 2015-05-01, 2015-04-01, 2015-02-01, 2014-11-01, 2014-06-01, 2014-04-01-preview, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: sites/instances/extensions
API: 2016-08-01, 2016-03-01, 2015-08-01, 2015-07-01, 2015-06-01, 2015-05-01, 2015-04-01, 2015-02-01, 2014-11-01, 2014-06-01, 2014-04-01-preview, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: sites/slots/instances/extensions
API: 2016-08-01, 2016-03-01, 2015-08-01, 2015-07-01, 2015-06-01, 2015-05-01, 2015-04-01, 2015-02-01, 2014-11-01, 2014-06-01, 2014-04-01-preview, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: publishingUsers
API: 2016-03-01, 2015-08-01, 2015-07-01, 2015-06-01, 2015-05-01, 2015-04-01, 2015-02-01, 2014-11-01, 2014-06-01, 2014-04-01-preview, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: ishostnameavailable
API: 2016-03-01, 2015-08-01, 2015-07-01, 2015-06-01, 2015-05-01, 2015-04-01, 2015-02-01, 2014-11-01, 2014-06-01, 2014-04-01-preview, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: sourceControls
API: 2016-03-01, 2015-08-01, 2015-07-01, 2015-06-01, 2015-05-01, 2015-04-01, 2015-02-01, 2014-11-01, 2014-06-01, 2014-04-01-preview, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: availableStacks
API: 2016-03-01, 2015-08-01, 2015-07-01, 2015-06-01, 2015-05-01, 2015-04-01, 2015-02-01, 2014-11-01, 2014-06-01, 2014-04-01-preview, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: listSitesAssignedToHostName
API: 2016-03-01, 2015-08-01, 2015-07-01, 2015-06-01, 2015-05-01, 2015-04-01, 2015-02-01

Locations: Germany Central, Germany Northeast
ResourceType: sites/hostNameBindings
API: 2016-08-01, 2016-03-01, 2015-08-01, 2015-07-01, 2015-06-01, 2015-05-01, 2015-04-01, 2015-02-01

Locations: Germany Central, Germany Northeast
ResourceType: sites/slots/hostNameBindings
API: 2016-08-01, 2016-03-01, 2015-08-01, 2015-07-01, 2015-06-01, 2015-05-01, 2015-04-01, 2015-02-01

Locations: Germany Central, Germany Northeast
ResourceType: operations
API: 2016-03-01, 2015-08-01, 2015-07-01, 2015-06-01, 2015-05-01, 2015-04-01, 2015-02-01, 2014-11-01, 2014-06-01, 2014-04-01-preview, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: certificates
API: 2016-03-01, 2015-08-01, 2015-07-01, 2015-06-01, 2015-05-01, 2015-04-01, 2015-02-01, 2014-11-01, 2014-06-01, 2014-04-01-preview, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: serverFarms
API: 2016-09-01, 2016-03-01, 2015-08-01, 2015-07-01, 2015-06-01, 2015-05-01, 2015-04-01, 2015-02-01, 2014-11-01, 2014-06-01, 2014-04-01-preview, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: sites
API: 2016-08-01, 2016-03-01, 2015-08-01, 2015-07-01, 2015-06-01, 2015-05-01, 2015-04-01, 2015-02-01, 2014-11-01, 2014-06-01, 2014-04-01-preview, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: sites/slots
API: 2016-08-01, 2016-03-01, 2015-08-01, 2015-07-01, 2015-06-01, 2015-05-01, 2015-04-01, 2015-02-01, 2014-11-01, 2014-06-01, 2014-04-01-preview, 2014-04-01

Locations:
ResourceType: runtimes
API: 2016-03-01, 2015-08-01, 2015-07-01, 2015-06-01, 2015-05-01, 2015-04-01, 2015-02-01, 2014-11-01, 2014-06-01, 2014-04-01

Locations:
ResourceType: georegions
API: 2016-03-01, 2015-08-01, 2015-07-01, 2015-06-01, 2015-05-01, 2015-04-01, 2015-02-01, 2014-11-01, 2014-06-01, 2014-04-01-preview, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: sites/premieraddons
API: 2016-08-01, 2016-03-01, 2015-08-01, 2015-07-01, 2015-06-01, 2015-05-01, 2015-04-01

Locations: Germany Central, Germany Northeast
ResourceType: hostingEnvironments
API: 2016-09-01, 2016-03-01, 2015-08-01, 2015-07-01, 2015-06-01, 2015-05-01, 2015-04-01, 2015-02-01, 2014-11-01, 2014-06-01, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: hostingEnvironments/multiRolePools
API: 2016-09-01, 2016-03-01, 2015-08-01, 2015-07-01, 2015-06-01, 2015-05-01, 2015-04-01, 2015-02-01, 2014-11-01, 2014-06-01, 2014-04-01

Locations: Germany Central, Germany Northeast
ResourceType: hostingEnvironments/workerPools
API: 2016-09-01, 2016-03-01, 2015-08-01, 2015-07-01, 2015-06-01, 2015-05-01, 2015-04-01, 2015-02-01, 2014-11-01, 2014-06-01, 2014-04-01

Locations:
ResourceType: hostingEnvironments/multiRolePools/instances
API: 2016-09-01, 2016-03-01, 2015-08-01, 2015-07-01, 2015-06-01, 2015-05-01, 2015-04-01, 2015-02-01, 2014-11-01, 2014-06-01, 2014-04-01-preview, 2014-04-01

Locations:
ResourceType: hostingEnvironments/workerPools/instances
API: 2016-09-01, 2016-03-01, 2015-08-01, 2015-07-01, 2015-06-01, 2015-05-01, 2015-04-01, 2015-02-01, 2014-11-01, 2014-06-01, 2014-04-01-preview, 2014-04-01

Locations:
ResourceType: deploymentLocations
API: 2016-03-01, 2015-08-01, 2015-07-01, 2015-06-01, 2015-05-01, 2015-04-01, 2015-02-01, 2014-11-01, 2014-06-01, 2014-04-01-preview, 2014-04-01

Locations:
ResourceType: ishostingenvironmentnameavailable
API: 2016-03-01, 2015-08-01, 2015-07-01, 2015-06-01, 2015-05-01, 2015-04-01, 2015-02-01, 2014-11-01, 2014-06-01, 2014-04-01-preview, 2014-04-01

Locations:
ResourceType: checkNameAvailability
API: 2015-08-01

ProviderId:/subscriptions/1e498be8-9b44-43e5-8a7e-96e59ecbfe78/providers/Microsoft.ADHybridHealthService
Locations: Germany Central, Germany NorthEast
ResourceType: services
API: 2014-01-01

Locations: Germany Central, Germany NorthEast
ResourceType: addsservices
API: 2014-01-01

Locations: Germany Central, Germany NorthEast
ResourceType: configuration
API: 2014-01-01

Locations: Germany Central, Germany NorthEast
ResourceType: operations
API: 2014-01-01

Locations: Germany Central, Germany NorthEast
ResourceType: agents
API: 2014-01-01

Locations: Germany Central, Germany NorthEast
ResourceType: aadsupportcases
API: 2014-01-01

Locations: Germany Central, Germany NorthEast
ResourceType: reports
API: 2014-01-01

Locations: Germany Central, Germany NorthEast
ResourceType: servicehealthmetrics
API: 2014-01-01

Locations: Germany Central, Germany NorthEast
ResourceType: logs
API: 2014-01-01

Locations: Germany Central, Germany NorthEast
ResourceType: anonymousapiusers
API: 2014-01-01

ProviderId:/subscriptions/1e498be8-9b44-43e5-8a7e-96e59ecbfe78/providers/Microsoft.Authorization
Locations:
ResourceType: roleAssignments
API: 2015-07-01, 2015-06-01, 2015-05-01-preview, 2014-10-01-preview, 2014-07-01-preview, 2014-04-01-preview

Locations:
ResourceType: roleDefinitions
API: 2015-07-01, 2015-06-01, 2015-05-01-preview, 2014-10-01-preview, 2014-07-01-preview, 2014-04-01-preview

Locations:
ResourceType: classicAdministrators
API: 2015-06-01, 2015-05-01-preview, 2014-10-01-preview, 2014-07-01-preview, 2014-04-01-preview

Locations:
ResourceType: permissions
API: 2015-07-01, 2015-06-01, 2015-05-01-preview, 2014-10-01-preview, 2014-07-01-preview, 2014-04-01-preview

Locations:
ResourceType: locks
API: 2016-09-01, 2015-06-01, 2015-05-01-preview, 2015-01-01

Locations:
ResourceType: operations
API: 2015-07-01, 2015-01-01, 2014-10-01-preview, 2014-06-01

Locations:
ResourceType: policyDefinitions
API: 2016-12-01, 2016-04-01, 2015-10-01-preview

Locations:
ResourceType: policyAssignments
API: 2016-12-01, 2016-04-01, 2015-10-01-preview

Locations:
ResourceType: providerOperations
API: 2015-07-01-preview, 2015-07-01

Locations:
ResourceType: elevateAccess
API: 2016-07-01, 2015-07-01, 2015-06-01, 2015-05-01-preview, 2014-10-01-preview, 2014-07-01-preview, 2014-04-01-preview

ProviderId:/subscriptions/1e498be8-9b44-43e5-8a7e-96e59ecbfe78/providers/Microsoft.Batch
Locations: Germany Central, Germany Northeast
ResourceType: batchAccounts
API: 2017-05-01, 2017-01-01, 2015-12-01, 2015-09-01, 2015-07-01, 2014-05-01-privatepreview

Locations: Germany Central, Germany Northeast
ResourceType: operations
API: 2017-05-01, 2017-01-01, 2015-12-01, 2015-09-01

Locations: Germany Central
ResourceType: locations
API: 2017-05-01, 2017-01-01, 2015-12-01, 2015-09-01

Locations: Germany Central, Germany Northeast
ResourceType: locations/quotas
API: 2017-05-01, 2017-01-01, 2015-12-01, 2015-09-01

ProviderId:/subscriptions/1e498be8-9b44-43e5-8a7e-96e59ecbfe78/providers/Microsoft.Cache
Locations: Germany Central, Germany NorthEast
ResourceType: Redis
API: 2016-04-01, 2015-08-01, 2015-03-01, 2014-04-01-preview, 2014-04-01-alpha, 2014-04-01

Locations:
ResourceType: locations
API: 2016-04-01, 2015-08-01, 2015-03-01, 2014-04-01-preview, 2014-04-01-alpha, 2014-04-01

Locations: Germany Central, Germany NorthEast
ResourceType: locations/operationResults
API: 2016-04-01, 2015-08-01, 2015-03-01, 2014-04-01-preview, 2014-04-01-alpha, 2014-04-01

Locations:
ResourceType: checkNameAvailability
API: 2016-04-01, 2015-08-01, 2015-03-01, 2014-04-01-preview, 2014-04-01-alpha, 2014-04-01

Locations:
ResourceType: operations
API: 2016-04-01, 2015-08-01, 2015-03-01, 2014-04-01-preview, 2014-04-01-alpha, 2014-04-01

ProviderId:/subscriptions/1e498be8-9b44-43e5-8a7e-96e59ecbfe78/providers/Microsoft.ClassicCompute
Locations: Germany Central, Germany Northeast
ResourceType: domainNames
API: 2016-04-01, 2015-12-01, 2015-10-01, 2015-06-01, 2014-06-01, 2014-01-01

Locations:
ResourceType: checkDomainNameAvailability
API: 2016-04-01, 2015-12-01, 2015-10-01, 2015-06-01, 2014-06-01, 2014-01-01

Locations: Germany Central, Germany Northeast
ResourceType: domainNames/slots
API: 2016-04-01, 2015-12-01, 2015-10-01, 2015-06-01, 2014-06-01, 2014-01-01

Locations: Germany Central, Germany Northeast
ResourceType: domainNames/slots/roles
API: 2016-04-01, 2015-12-01, 2015-10-01, 2015-06-01, 2014-06-01, 2014-01-01

Locations: Germany Central, Germany Northeast
ResourceType: virtualMachines
API: 2016-04-01, 2015-12-01, 2015-10-01, 2015-06-01, 2014-06-01, 2014-04-01, 2014-01-01

Locations:
ResourceType: capabilities
API: 2016-04-01, 2015-12-01, 2015-10-01, 2015-06-01, 2014-06-01

Locations:
ResourceType: quotas
API: 2016-04-01, 2015-12-01, 2015-10-01, 2015-06-01, 2014-06-01, 2014-01-01

Locations:
ResourceType: operations
API: 2016-04-01, 2015-12-01, 2015-10-01, 2015-06-01, 2014-06-01, 2014-04-01, 2014-01-01

Locations:
ResourceType: resourceTypes
API: 2016-04-01, 2015-12-01, 2015-10-01, 2015-06-01, 2014-06-01

Locations:
ResourceType: moveSubscriptionResources
API: 2016-04-01, 2015-12-01, 2015-10-01

Locations:
ResourceType: validateSubscriptionMoveAvailability
API: 2016-04-01, 2015-12-01, 2015-10-01

Locations:
ResourceType: operationStatuses
API: 2016-04-01, 2015-12-01, 2015-10-01

Locations:
ResourceType: operatingSystems
API: 2016-04-01, 2015-12-01, 2015-10-01, 2015-06-01, 2014-06-01, 2014-04-01, 2014-01-01

Locations:
ResourceType: operatingSystemFamilies
API: 2016-04-01, 2015-12-01, 2015-10-01, 2015-06-01, 2014-06-01, 2014-04-01, 2014-01-01

ProviderId:/subscriptions/1e498be8-9b44-43e5-8a7e-96e59ecbfe78/providers/Microsoft.ClassicNetwork
Locations: Germany Central, Germany Northeast
ResourceType: virtualNetworks
API: 2016-04-01, 2015-12-01, 2015-06-01, 2014-06-01, 2014-01-01

Locations: Germany Central, Germany Northeast
ResourceType: reservedIps
API: 2016-04-01, 2015-12-01, 2015-06-01, 2014-06-01, 2014-01-01

Locations:
ResourceType: quotas
API: 2016-04-01, 2015-12-01, 2015-06-01, 2014-06-01, 2014-01-01

Locations:
ResourceType: gatewaySupportedDevices
API: 2016-04-01, 2015-12-01, 2015-06-01, 2014-06-01, 2014-01-01

Locations:
ResourceType: operations
API: 2016-04-01, 2015-12-01, 2015-06-01, 2014-06-01, 2014-04-01, 2014-01-01

Locations: Germany Central, Germany Northeast
ResourceType: networkSecurityGroups
API: 2016-04-01, 2015-12-01, 2015-06-01

Locations:
ResourceType: capabilities
API: 2016-04-01, 2015-12-01, 2015-10-01, 2015-06-01, 2014-06-01

ProviderId:/subscriptions/1e498be8-9b44-43e5-8a7e-96e59ecbfe78/providers/Microsoft.ClassicStorage
Locations: Germany Central, Germany Northeast
ResourceType: storageAccounts
API: 2016-04-01, 2015-12-01, 2015-06-01, 2014-06-01, 2014-04-01-beta, 2014-04-01, 2014-01-01

Locations:
ResourceType: quotas
API: 2016-04-01, 2015-12-01, 2015-06-01, 2014-06-01, 2014-01-01

Locations:
ResourceType: checkStorageAccountAvailability
API: 2016-04-01, 2015-12-01, 2015-06-01, 2014-06-01, 2014-01-01

Locations:
ResourceType: capabilities
API: 2016-04-01, 2015-12-01, 2015-06-01, 2014-06-01

Locations:
ResourceType: disks
API: 2016-04-01, 2015-12-01, 2015-06-01, 2014-06-01

Locations:
ResourceType: images
API: 2016-04-01, 2015-12-01, 2015-06-01, 2014-06-01

Locations:
ResourceType: publicImages
API: 2016-04-01

Locations:
ResourceType: osImages
API: 2016-04-01, 2015-12-01, 2015-06-01, 2014-06-01

Locations:
ResourceType: operations
API: 2016-04-01, 2015-12-01, 2015-06-01, 2014-06-01, 2014-04-01, 2014-01-01

ProviderId:/subscriptions/1e498be8-9b44-43e5-8a7e-96e59ecbfe78/providers/Microsoft.ClassicInfrastructureMigrate
Locations: Germany Northeast, Germany Central
ResourceType: classicInfrastructureResources
API: 2015-06-15

ProviderId:/subscriptions/1e498be8-9b44-43e5-8a7e-96e59ecbfe78/providers/Microsoft.Compute
Locations: Germany Central, Germany Northeast
ResourceType: availabilitySets
API: 2017-03-30, 2016-08-30, 2016-04-30-preview, 2016-03-30, 2015-06-15, 2015-05-01-preview

Locations: Germany Central, Germany Northeast
ResourceType: virtualMachines
API: 2017-03-30, 2016-08-30, 2016-04-30-preview, 2016-03-30, 2015-06-15, 2015-05-01-preview

Locations: Germany Central, Germany Northeast
ResourceType: virtualMachines/extensions
API: 2017-03-30, 2016-08-30, 2016-04-30-preview, 2016-03-30, 2015-06-15, 2015-05-01-preview

Locations: Germany Central, Germany Northeast
ResourceType: virtualMachineScaleSets
API: 2017-03-30, 2016-08-30, 2016-04-30-preview, 2016-03-30, 2015-06-15, 2015-05-01-preview

Locations: Germany Central, Germany Northeast
ResourceType: virtualMachineScaleSets/extensions
API: 2017-03-30, 2016-08-30, 2016-04-30-preview, 2016-03-30, 2015-06-15, 2015-05-01-preview

Locations: Germany Central, Germany Northeast
ResourceType: virtualMachineScaleSets/virtualMachines
API: 2017-03-30, 2016-08-30, 2016-04-30-preview, 2016-03-30, 2015-06-15, 2015-05-01-preview

Locations: Germany Central, Germany Northeast
ResourceType: virtualMachineScaleSets/networkInterfaces
API: 2017-03-30, 2016-09-01, 2016-08-01, 2016-07-01, 2016-06-01, 2016-03-30, 2015-06-15, 2015-05-01-preview

Locations: Germany Central, Germany Northeast
ResourceType: virtualMachineScaleSets/virtualMachines/networkInterfaces
API: 2017-03-30, 2016-09-01, 2016-08-01, 2016-07-01, 2016-06-01, 2016-03-30, 2015-06-15, 2015-05-01-preview

Locations: Germany Central, Germany Northeast
ResourceType: virtualMachineScaleSets/publicIPAddresses
API: 2017-03-30

Locations:
ResourceType: locations
API: 2017-03-30, 2016-08-30, 2016-04-30-preview, 2016-03-30, 2015-06-15, 2015-05-01-preview

Locations: Germany Central, Germany Northeast
ResourceType: locations/operations
API: 2017-03-30, 2016-08-30, 2016-04-30-preview, 2016-03-30, 2015-06-15, 2015-05-01-preview

Locations: Germany Central, Germany Northeast
ResourceType: locations/vmSizes
API: 2017-03-30, 2016-08-30, 2016-04-30-preview, 2016-03-30, 2015-06-15, 2015-05-01-preview

Locations: Germany Central, Germany Northeast
ResourceType: locations/runCommands
API: 2017-03-30

Locations: Germany Central, Germany Northeast
ResourceType: locations/usages
API: 2017-03-30, 2016-08-30, 2016-04-30-preview, 2016-03-30, 2015-06-15, 2015-05-01-preview

Locations: Germany Central, Germany Northeast
ResourceType: locations/virtualMachines
API: 2017-03-30, 2016-08-30

Locations: Germany Central, Germany Northeast
ResourceType: locations/publishers
API: 2017-03-30, 2016-08-30, 2016-04-30-preview, 2016-03-30, 2015-06-15, 2015-05-01-preview

Locations: Germany Central, Germany Northeast
ResourceType: operations
API: 2017-03-30, 2016-08-30, 2016-03-30, 2015-06-15, 2015-05-01-preview

Locations: Germany Central, Germany Northeast
ResourceType: restorePointCollections
API: 2017-03-30

Locations: Germany Central, Germany Northeast
ResourceType: restorePointCollections/restorePoints
API: 2017-03-30

Locations: Germany Central, Germany Northeast
ResourceType: disks
API: 2017-03-30, 2016-04-30-preview

Locations: Germany Central, Germany Northeast
ResourceType: snapshots
API: 2017-03-30, 2016-04-30-preview

Locations: Germany Central, Germany Northeast
ResourceType: locations/diskoperations
API: 2017-03-30, 2016-04-30-preview

Locations: Germany Central, Germany Northeast
ResourceType: images
API: 2017-03-30, 2016-04-30-preview

ProviderId:/subscriptions/1e498be8-9b44-43e5-8a7e-96e59ecbfe78/providers/Microsoft.Features
Locations:
ResourceType: features
API: 2015-12-01, 2014-08-01-preview

Locations:
ResourceType: providers
API: 2015-12-01, 2014-08-01-preview

ProviderId:/subscriptions/1e498be8-9b44-43e5-8a7e-96e59ecbfe78/providers/Microsoft.HDInsight
Locations: Germany Central, Germany Northeast
ResourceType: clusters
API: 2015-03-01-preview

Locations:
ResourceType: clusters/applications
API: 2015-03-01-preview

Locations:
ResourceType: clusters/operationresults
API: 2015-03-01-preview

Locations: Germany Central, Germany Northeast
ResourceType: locations
API: 2015-03-01-preview

Locations:
ResourceType: locations/capabilities
API: 2015-03-01-preview

Locations:
ResourceType: locations/operationresults
API: 2015-03-01-preview

Locations:
ResourceType: locations/azureasyncoperations
API: 2015-03-01-preview

Locations:
ResourceType: locations/validateCreateRequest
API: 2015-03-01-preview

Locations:
ResourceType: operations
API: 2015-03-01-preview

ProviderId:/subscriptions/1e498be8-9b44-43e5-8a7e-96e59ecbfe78/providers/Microsoft.ImportExport
Locations: Germany Central, Germany Northeast
ResourceType: jobs
API: 2016-11-01, 2016-07-01-preview

Locations: Germany Central, Germany Northeast
ResourceType: locations
API: 2016-11-01, 2016-07-01-preview

Locations: Germany Central, Germany Northeast
ResourceType: locations/operationResults
API: 2016-11-01, 2016-07-01-preview

Locations: Germany Central, Germany Northeast
ResourceType: operations
API: 2016-11-01, 2016-07-01-preview

ProviderId:/subscriptions/1e498be8-9b44-43e5-8a7e-96e59ecbfe78/providers/Microsoft.KeyVault
Locations: Germany Central, Germany Northeast
ResourceType: vaults
API: 2016-10-01, 2015-06-01

Locations: Germany Central, Germany Northeast
ResourceType: vaults/secrets
API: 2016-10-01, 2015-06-01

Locations: Germany Central, Germany Northeast
ResourceType: vaults/accessPolicies
API: 2016-10-01, 2015-06-01

Locations:
ResourceType: operations
API: 2016-10-01, 2015-06-01

Locations:
ResourceType: checkNameAvailability
API: 2016-10-01, 2015-06-01

ProviderId:/subscriptions/1e498be8-9b44-43e5-8a7e-96e59ecbfe78/providers/Microsoft.MachineLearning
Locations: Germany Central
ResourceType: Workspaces
API: 2016-04-01

ProviderId:/subscriptions/1e498be8-9b44-43e5-8a7e-96e59ecbfe78/providers/Microsoft.Media
Locations: Germany Central, Germany Northeast
ResourceType: mediaservices
API: 2015-10-01

Locations:
ResourceType: operations
API: 2015-10-01

Locations:
ResourceType: checknameavailability
API: 2015-10-01

ProviderId:/subscriptions/1e498be8-9b44-43e5-8a7e-96e59ecbfe78/providers/Microsoft.Portal
Locations: Germany Northeast, Germany Central
ResourceType: dashboards
API: 2015-08-01-preview

Locations:
ResourceType: operations
API: 2015-08-01-preview

ProviderId:/subscriptions/1e498be8-9b44-43e5-8a7e-96e59ecbfe78/providers/Microsoft.PowerBI
Locations: Germany Northeast, Germany CENTRAL
ResourceType: workspaceCollections
API: 2016-01-29

Locations:
ResourceType: locations
API: 2016-01-29

Locations: Germany Northeast, Germany CENTRAL
ResourceType: locations/checkNameAvailability
API: 2016-01-29

ProviderId:/subscriptions/1e498be8-9b44-43e5-8a7e-96e59ecbfe78/providers/Microsoft.RecoveryServices
Locations: Germany Northeast, Germany Central
ResourceType: vaults
API: 2016-12-01, 2016-08-10, 2016-06-01, 2016-05-01, 2015-12-15, 2015-12-10, 2015-11-10, 2015-08-15, 2015-08-10, 2015-06-10, 2015-03-15

Locations: Germany Northeast
ResourceType: operations
API: 2016-08-10, 2016-06-01, 2015-12-15, 2015-12-10, 2015-11-10, 2015-08-15, 2015-08-10, 2015-06-10, 2015-03-15

Locations:
ResourceType: locations
API: 2016-06-01

Locations: Germany Northeast, Germany Central
ResourceType: locations/backupStatus
API: 2016-06-01

Locations: Germany Northeast, Germany Central
ResourceType: locations/allocatedStamp
API: 2016-06-01

Locations: Germany Northeast, Germany Central
ResourceType: locations/allocateStamp
API: 2016-06-01

ProviderId:/subscriptions/1e498be8-9b44-43e5-8a7e-96e59ecbfe78/providers/Microsoft.Relay
Locations: Germany Central, Germany Northeast
ResourceType: namespaces
API: 2016-07-01

Locations:
ResourceType: checkNameAvailability
API: 2016-07-01

Locations:
ResourceType: operations
API: 2016-07-01

ProviderId:/subscriptions/1e498be8-9b44-43e5-8a7e-96e59ecbfe78/providers/Microsoft.ResourceHealth
Locations:
ResourceType: availabilityStatuses
API: 2015-01-01

Locations:
ResourceType: operations
API: 2015-01-01

ProviderId:/subscriptions/1e498be8-9b44-43e5-8a7e-96e59ecbfe78/providers/Microsoft.Resources
Locations:
ResourceType: tenants
API: 2016-06-01, 2016-02-01, 2015-11-01, 2015-01-01, 2014-04-01-preview

Locations:
ResourceType: locations
API: 2016-06-01, 2016-02-01, 2015-11-01, 2015-01-01, 2014-04-01-preview

Locations:
ResourceType: providers
API: 2016-06-01, 2016-02-01, 2015-11-01, 2015-01-01, 2014-04-01-preview

Locations:
ResourceType: checkresourcename
API: 2016-06-01, 2016-02-01, 2015-11-01, 2015-01-01, 2014-04-01-preview

Locations:
ResourceType: resources
API: 2016-06-01, 2016-02-01, 2015-11-01, 2015-01-01, 2014-04-01-preview

Locations:
ResourceType: subscriptions
API: 2016-06-01, 2016-02-01, 2015-11-01, 2015-01-01, 2014-04-01-preview

Locations:
ResourceType: subscriptions/resources
API: 2016-06-01, 2016-02-01, 2015-11-01, 2015-01-01, 2014-04-01-preview

Locations:
ResourceType: subscriptions/providers
API: 2016-06-01, 2016-02-01, 2015-11-01, 2015-01-01, 2014-04-01-preview

Locations:
ResourceType: subscriptions/operationresults
API: 2016-06-01, 2016-02-01, 2015-11-01, 2015-01-01, 2014-04-01-preview

Locations: Germany Central, Germany Northeast
ResourceType: resourceGroups
API: 2016-06-01, 2016-02-01, 2015-11-01, 2015-01-01, 2014-04-01-preview

Locations: Germany Central, Germany Northeast
ResourceType: subscriptions/resourceGroups
API: 2016-06-01, 2016-02-01, 2015-11-01, 2015-01-01, 2014-04-01-preview

Locations:
ResourceType: subscriptions/resourcegroups/resources
API: 2016-06-01, 2016-02-01, 2015-11-01, 2015-01-01, 2014-04-01-preview

Locations:
ResourceType: subscriptions/locations
API: 2016-06-01, 2016-02-01, 2015-11-01, 2015-01-01, 2014-04-01-preview

Locations:
ResourceType: subscriptions/tagnames
API: 2016-06-01, 2016-02-01, 2015-11-01, 2015-01-01, 2014-04-01-preview

Locations:
ResourceType: subscriptions/tagNames/tagValues
API: 2016-06-01, 2016-02-01, 2015-11-01, 2015-01-01, 2014-04-01-preview

Locations:
ResourceType: deployments
API: 2016-06-01, 2016-02-01, 2015-11-01, 2015-01-01, 2014-04-01-preview

Locations:
ResourceType: deployments/operations
API: 2016-06-01, 2016-02-01, 2015-11-01, 2015-01-01, 2014-04-01-preview

Locations:
ResourceType: operations
API: 2015-01-01

ProviderId:/subscriptions/1e498be8-9b44-43e5-8a7e-96e59ecbfe78/providers/Microsoft.Scheduler
Locations: Germany Central, Germany Northeast
ResourceType: jobcollections
API: 2016-03-01, 2016-01-01, 2014-08-01-preview

Locations: Germany Central, Germany Northeast
ResourceType: operations
API: 2016-03-01, 2016-01-01, 2014-08-01-preview

Locations: Germany Central, Germany Northeast
ResourceType: operationResults
API: 2016-03-01, 2016-01-01, 2014-08-01-preview

ProviderId:/subscriptions/1e498be8-9b44-43e5-8a7e-96e59ecbfe78/providers/Microsoft.ServiceFabric
Locations: Germany Central, Germany Northeast
ResourceType: clusters
API: 2016-09-01, 2016-03-01, 2016-01-01-beta, 2015-01-01-alpha

Locations:
ResourceType: locations
API: 2016-09-01, 2016-03-01

Locations: Germany Central, Germany Northeast
ResourceType: locations/clusterVersions
API: 2016-09-01, 2016-03-01, 2016-01-01-beta, 2015-01-01-alpha

ProviderId:/subscriptions/1e498be8-9b44-43e5-8a7e-96e59ecbfe78/providers/microsoft.support
Locations: Germany Central, Germany Northeast
ResourceType: operations
API: 2015-07-01-Preview, 2015-03-01

Locations: Germany Central, Germany Northeast
ResourceType: supporttickets
API: 2015-07-01-Preview, 2015-03-01

IotHub Device Twin ‘UnauthorizedException’

Damir Dobric — Mon, 12 Jun 2017 05:55:00 GMT

When working with device twins and IoTHub, you have to be aware of security requirements of certain methods of the service twin API.

For example to get the instance of the twin or to update the twin you will need ‘ServiceConnect’ permission.

var twin = await registryManager.GetTwinAsync(Credentials.DeviceId);

await registryManager.UpdateTwinAsync(twin.DeviceId, patch, twin.ETag);

However, if you want to query for twin properties you will need ‘RegistryRead’ permission.

var query = registryManager.CreateQuery("SELECT * FROM devices WHERE tags.location.plant = 'Redmond43'", 100);

var twinsInRedmond43 = await query.GetNextAsTwinAsync();

If you want to be sure that combination of statements listed above works well, you need to set the service SAS policy with ServiceConnect and RegistryRead permission.

If this is not the case, one of operations might fail with:

Microsoft.Azure.Devices.Common.Exceptions.UnauthorizedException:

Mastering IoT Solutions using Microsoft Azure Platform

Damir Dobric — Sat, 27 May 2017 16:24:36 GMT

It is obvious that Cloud, BigData and IoT becoming true mega trends. They are consisted technological part for Digital Transformation process, which has a massive impact on every architect and developer.

In this break-out session, we will dive deep in some of most IoT relevant Microsoft Azure services like AppService, APIApps and IoTHub. We will demonstrate how these services can help to easy build IoT solutions. But, you will also learn how to extend existing services with features, which are not necessarily a part of a common IoT solution.

You will see how devices like Amazon Echo Dot can be integrated in the Microsoft Azure and Windows IoT platform.

Best Practices for Building IoT Solutions on Microsoft platform

Damir Dobric — Sat, 27 May 2017 16:11:13 GMT

The true story – Ask Experts

I'm usually giving deep technical sessions with lot of demos and code. However, this time we have organized Ask-Experts Break-Out Session.

This is an interactive technical session. Attendees can ask questions related to IoT and we will try to help. WE can talk about IoT Services, specific solutions, Case Studies etc.

We will also discuss about how IoT mega trend is aggressively shifting our skill focus, what does this mean for our education and how we are mastering it.