Monthly Archives: May 2015

What’s actually new in Windows 10

So far for those that have been part of the windows insider preview, most have been caught up with the GUI, which of course is an important aspect on how user friendly the operating system has become.

And some have been speculating on what Microsoft actually are doing since the GUI has been coming along pretty slow, but most haven’t looked at how much is new in Windows 10, so therefore I decided to write this post. So no I not gonna dive into Cortana and Microsoft Edge… this is pretty much covered on every windows blog.

Windows 8


Windows 10



Now lets start with some of the pretty known facts:

Universal Applications

Which is modern type appliations (which started in Windows 8) but is rewamped in Windows 10 which pretty much allows developers to create the same application for all Windows 10 platforms, so like Office Preview which is in the Windows Store will appear the same on mobile as on a desktop computer. Since the universal apps are from the modern application framework they are bound to the same lifecycle which I will cover in a bit.

Now problem with modern applications when it came in Windows 8 was that the ones that microsoft created werent that great, now they made some other examples which actually shows how great they are!

Microsoft has already created some examples like

Mail & Calender
Microsoft Edge (Which will be the standard Browser in Windows 10)

Also announced that Dropbox will be created a universal appliation which will be released late this year as well.

Now modern applications are actually a pretty good idea, problem is that it was “forced” upon us in Windows 8 but for those that aren’t familiar with it, the applications are bound within a lifecycle which defines how an app applications is going to happen. They don’t do any registry writes and therefore do not clutter your registry, they are isolated and run within a container.

you cannot run an modern application as administrator so you cannot elevate the level of integrity of the application. The applications need to be signed and can only be installed either via the Store or sideloaded using for instance System Center.

Problem is that most buisnesses still use regular Win32 based applications, which cannot be pushed via the Store. Microsoft is working on a solution which is called Project Centennial which allows us to convert Win32 based application and force them to work within the boundaries of a modern application, kinda like a app-v based application. Which will in essence allow Microsoft to bridge existing applications to modern applications, read more here –>


Windows update for buisness & Windows As a Service

One of the most known factors is that Windows 10 will be the last Windows desktop version, since the last 30 years, Windows has been shipped in the same way. Microsoft creates a new operating system ships it with OEM, sells physical media like floppy, cd, dvd and so on. With Windows 10 all with be with Windows 10 and Microsoft will be constantly created new builds of it and shipping it using Windows update. Which will be like most mobile users are familiar with on Android and IOs.

And also with this Microsoft also created a cloud based update solution called Windows update for buisness which is in essence a smaller cloud based WSUS. Which will allow buisnesses to control updates and builds going to their computers.

Moving forward all new builds will be first tested internally in Microsoft, then it will be moved out to those who have signed up on the Windows Insider program and then be pushed out to the consumers using Windows update and then come to the first branch on Windows Update for Buisness.



 So I essence Windows As a Service is a pretty nifty Update sequence set in motion actually. And Windows Update for Buisness is a cloud based service to actually control it. Now it will have some other features as well such as.

Peer-to-Peer seeding (Meaning that a client can share binaries with other clients within a network for instance)

Maintance time (When can we ship updates)

Deployment Rings (Who gets the builds first for instance, based on Computer Groups)

Important to note that this will be offered as a free service, but will be most likely aimed at users of Windows Enterprise.

Also as a part of this Microsoft is also releasing a new private store which as aimed at the same type of buisnesses, called Windows Store for Buisness.


Windows Store for Buisness


Now this will be a private section within the Microsoft Store where users can authenticate with their Azure Active Directory user and get access to LoB application which for instance their IT-guy have published. This is also a free service which can eventually be accessed from

At first release it will only support Azure Active Directory users, but it will also allow for licens management and offlice access meaning that users dont have to download large applications from the internet, but be redirected to a internal network share to get an application, and with the coming of project centennial we can also eventually published Win32 applications within the store as well. But as with all the other stuff it will be possible to manage it using System Center or Intune.


Security features

Now this is where things get interesting, and where many have actually havent paid attention on what Microsoft has been doing with Windows 10.

There are many new enhancements here but Im going to name some of them and what they can do.¨


VSM (Virtual Secure Mode)

Im guesing that most have heard about pass-the-hash and Mimikats ? NTLM has some known security issues which allows some fortune ones to get access to a NTLM hash of a administrator user.


When a hacker has access to this hash well, we can pretty much enter everyone. This is because of the LSA service. In Windows 10 Microsoft did something creative, with VSA what they actually do is isolate the LSA service within a virtual machine running a coreOS subset on Hyper-V. This means that a regular Windows user is not able to gain access to the hash of a user since they arent allowed to communicate with the LSA service.


Windows Defender

Now this is the same engine as Security Essentials, Endpoint Protection and so on. This is not a new feature in Windows 10 but it has a huge number of improvements.

First of it now has an network IDS feature which will analyze the network traffic, because if your system is already infected and defender cannot spot it, the only way it can is to check the traffic.

Windows Defender will also now become an isolated process, because in the previous versions, defender was a regular service which if a system was defected it could be turned off. Now as an isolated service a virus/malware or something cannot turn of the service.

Also Microsoft has stated that if a user has another type of security software installed like Symantec or trend for instance and that software expires, after 3 days Microsoft will activate Windows defender again. Also Defender has been included in WinRE (Recovery Enviroment) which allows us to run malware scans without starting the actuall operatingsystem.

Windows Hello

Which is a builtin biometric authentication system, this allows us to authenticate using who we are, for instance it can be facial recognition, iris scan or fingerprint. This is not something new, but this is the first time that Microsoft has built-in this features into the operatingsystem. This is also a framework which will allow users to authenticate to other resources using biometric.

Next-Generation Credentials

Now the problem with todays infrastructure is that authentications are based upon username and passwords. Where it can be easy for hackers or someone else to be able to snif out the username and password and use it to gain access to resources.


With Next-generation credentials, Microsoft is creating a two-factor authentication system, where YOU is one of the factors (Windows Hello) and another factor might be the device itself, using either an asymmetric key which is stored in the TPM or can be a traditional certificate on the device. This essentially means that in order for a hacker to get your info he needs to steal your device and yourself…

This will also be allowed to be used as a SSO provider against different services, but will be first implemented in Azure AD where this will allow for a secure authentication process.

Enterprise Data Protection

Which is a security feature which will be able to sort between buisness data and private data. It allows for data to be automatically be encrypted on a end users device. And yes this is a feature which is coming for mobile and desktops


We will be able to define 4 different levels of security.

  • Block (We can say that users are NOT allowed to share data from a buisness file to for instance social media)
  • Override (Users get a warning but are allowed to override, events are logged)
  • Audit (Everything is logged)
  • Off

So this in coop with for instance Azure RMS opens to some pretty interesting stuff.

Device Guard

Ever tried Applocker ? Is was a good idea to be able to lock down what kind of applications a user were able to execute, problem was that is was only running in software meaning that you could bypass it, shut down the service and so on. Therefore Microsofot decided to take it to the next level by creating Device guard, which is a hardware assisted application locker, which only allows signed applications to run on a system. This feature will only be in Windows Enterprise and requires UEFI and Intel VT-X or AMD-V and also requires some specific hardware but many OEM partners like Lenovo, Dell and HP are creating new devices which will support this feature. Microsoft is also creating tools which allow us to sign application to be trusted with Device guard.

Health Attestation Service

This is a feature that came with Windows 8.1 but is improved vastly in Windows 10, this is a feature which allows Windows 10 to do a health check to the cloud before gaining access to internal resources. This will check features like SecureBoot, DEP, Bitlocker, AV status, Patch level and so on. You can see the OMA URL CSP set here –>


And regarding MDM, Microsoft has done alot already in preperation for Windows 10, and for those wondering, yes Intune supports Windows 10 now and can already now push OMA URI settings for Windows 10, all the settings can be found in the same list –>

So what else is new that isn’t that known ?

DirectX 12 support
MKV support
Print to PDF support
Azure AD Domain join support
Packet Manager with Powershell v5

Here is also an upgrade Matrix for those that are wondering what options you have


When to use Traffic Manager, Cloud Service Load balancing or Citrix Netscaler

Now that Citrix released their Netscaler appliance on Azure we have a huge option to do load balancing within the Azure platform. It is also important to think about the other options we have in Azure to do load balancing outside of Netscaler.

Traffic Manager is one of the first options which acts kinda like GSLB which is a DNS based load balancing feature. Which allow us to load balance between endpoints on a cloud service

1. Performance Load-Balancing

These services can be spread across different regions. This can either be load balanced based upon performance, round robin or failover.

Problem with DNS based load balancing is that is never gets a full overview of how the traffic is balanced since it basically just spreads the DNS responses. + at Traffic Manager has limited monitoring capabilities since it can only see on HTTP or HTTPS protocol.

We also now have support for nested profiles within Traffic Manager —

2. Nested Load-Balancing, Performance   Weights

Now on the other side we have load balancing endpoints on Cloud Services.


When setting up Cloud Services Load balancing we have more option depending on load balancing distribution, ref

We can have persistency based upon sourceIP or destionationIP for instance, and that we have more monitoring endbpoint based options. This is a more L4 based load balancing approach, which is also a free option to in Azure.

While Netscaler is a complete L4 – L7 load balancing platform which can be used to load balanced based upon many different parameters. Now you can also combine the Netscaler appliance with a HA setup to get the best from both worlds. With also giving you a active/active Netscaler setup within a cloud service

So when do use the different services ?

If you have a simple web-service which does not require a advanced monitor capabilities and are setup on many different cloud services, use Traffic Manager

If you have a service which are setup within a cloud service which you need to setup a simple load balancing capability on while having low cost, use Load Balanced Endpoints

If you have a service which requires a more advanced service monitoring capabilities and special demand to distribute traffic use Netscaler within a Cloud Serivce.

Getting started with Azure Resource Manager and visual studio

So for the few observant IT-pros, there has been a large fuzz around Azure and the new Azure Resource Manager, which is a new way to manage resources in Azure. In essence in a new architectutal design from Microsoft on how to manage IaaS resources.

Now to think about resource manager, it is a simple thing to think about different components that create a service which we want to deliver.

For instance if we want to deliver a e-commerce webshop using Azure, we would have multiple components like a DB-tier, Web-tier and maybe an application-tier. So instead of creating these components within a cloud service, we would create them inside a resource group in Azure.


Now Microsoft announced during Build a huge list of different templates that can get us started with ARM. These templates contain different JSON files that describe how a resource should be setup. This is essentially the version 2 of IaaS resources in Azure, instead of being managed within a cloud services we instead have all the different resources which are attached together without thinking about the cloud services, which has always been there because of the early days of PaaS.

You can find the different JSON templates here —

Which has a template for most of the different services included in Azure. Now we can also deploy resources directly from the GitHub repository, but this blog post will focus on using Visual Studio. (The templates will be able to be used directly in the management portal and you can just enter the paramteres as needed. )


This makes it easy to create a custom template for a deployment and reuse it for other customers for instance. You can also attach script which need to be run on a virtual machine instnances that are created after provisioning.

Now you can download the templates from Microsoft either using the GitHub client for versioning or you can download using a Zip option site. Using GitHub option allows to always have the templates in sync, if there are changes and so on.

Now in order to use Visual Studio and be able to use it with Resource manager you need a supported version of VS (2012, 2013 or 2015 RC, ill be using RC 2015) and you also need a copy of the latest Azure SDK which can be found here

Now after you have installed both you should have a new option when creating a new project


If this is not appearing, it might be that you need to repair the installtion of the Azure SDK. Now after you create a new project you will have the option to choose from different templates that is provided with the SDK


But i’m going to choose a blank template and add some resources and then use some of the different templates that Microsoft has created.

Now the project will be created with some files. You have the deploy azureresourcegroup powershell script which is used to actually create and deploy a resourcegroup using the templates files. Azcopy is used within the script to upload the template to a storage container.


Now by default the template is of course empty, so we need to add some resources to it.



Now this also gives a list of resources that can be added to the template.


So these templates also verify what prerequisites are needed to the tempalte


We can now also see that when we added a storage account, virtual network and a virtual machine a bunch of paramteres are added to the JSON template


If we drill into some of the paramteres we can see what kind of values are allowed. For instance on StorageAccountType


We can see that the default value for the Storage Account is Locally redundant in the template, we can change the value if we want to. These we need to chage before deploying it. For instance also VM username and password are not set and we need to define those values before deploying it or else the deployment will fail.,

Then we also have some variables that we can alter, for instance vNet subnet prefix and IP prenix.


After we are done adding our components and defining our variables and paramteres to the project we can deploy it by right clicking on the resource group in the solution explorer and choosing new deployment


Then choose a Microsoft Azure account and a valid subscription


And then choose Deploy, make sure to follow on the output window in Visual Studio to make sure that you dont get any error messages. Because it will validate the paramteres that are inserted to see if they comply or if you hare missing any information.

NOTE: you will also get this dialog box if there are some paramters that are not entered


Now after we have deployed the resource group template we can verify that it is there by going into the Azure Portal and looking into the resource group


Now that the resource group is there, if we need to do any updates like for instance change a virtual machine instance size we can just update the project and re-deplopy it, it will then update the virtual machine.

But note that this is still under preview and should not be used in production stuff in Azure quite yet, and using templates from GitHub for some reason the JSON outline view does not appear.

Implementing Citrix Netscaler on Azure

So this week, Citrix finally launched Netscaler on Azure. The reason why they couldnt do this before well there has been alot of limitations on Azure and there still are so therefore the appliance itself is also a bit limited, but ill get to that.

So whats important to know about Netscaler on Azure, is that

  • Its bring your own license
  • Runs as a A2 Linux instance (Which costs about 44$ a month) by default, this can be changed.
  • Runs in single IP mode (meaning that VIP – SNIP and NSIP run using the same IP
  • Bandwidth is also an extra cost on Azure (Meaning traffic that is going out of Microsofts datacentres)
  • Since it runs a single IP mode you do not need to enter a SNIP address (even thou the welcome configuration wizard will bug you about it)
  • Runs a custom firmware build Build 51.1048.e, and you we cannot upgrade it.
  • Adding a Azure DNS server should be done using TCP not UDP’’
  • IP is given using the DHCP service of Azure
  • Use the Static IP address feature in Azure to avoid changing IP address in case of reboots and so on.
  • There are some features which are not supported

Gratuitous ARP (GARP)
L2 Mode
Tagged VLAN
Dynamic Routing
Virtual MAC (VMAC)
CloudBridge Connector

Note that we can also use multiple NICs within Azure, this allows to have multiple NICs on a Netscaler intance, but Citrix does not recommend using this feature, and therefore the regular Netscaler VPX in Azure has 1 NIC.

VPX 10, 200 and 1000 is supported in Azure. If you need to have the VPX 1000 you need to scale up the virtual machine in order to support the amount of bandwidth. Since a medium machine A2 instance only supports up to 200 mbps of bandwidth

So now that we know some about how do we set it up ? The easiest way is by using the Marketplace feature in Azure (This requires an active subscription, but can also be setup if you have for instance an MSDN partner sub)


Just search for Citrix and you can find it there.

Now you need to enter a password (or public key) for SSH for the nsroot user. Make sure that by default it is a A2 istance, which I mentioned has limits for bandwidth.


Now we nee to alter some networking configurations as well, before we can create the VPX. By default IP is set by DHCP in Azure, but this can changed to static by using the new portal


And we have two options, one for VIP (Which is the external public IP address) and the Private IP internal address. You should change them both (VIP to Reserved) and Private range to static to be sure that the IP is static on the VPX in case of reboot and such.

Also be sure to add other endspoints if you for instance want to manage the VPX using HTTP/HTTPS, by default only SSH is added as an endpoint


After the provisioning is done you can now access the VPX using the public DNS address.


And voila!


Important to remember when setting up public services that you cannot use the following ports for external services

The following ports are reserved by the NetScaler virtual machine. You cannot define these as private ports when using the cloud service IP address for requests from the Internet.

Ports 21, 22, 80, 443, 8080, 67, 161, 179, 500, 520, 3003, 3008, 3009, 3010, 3011, 4001, 5061, 9000, 7000.

Taking Azure DNS preview for a spin!

Earlier this week, Microsoft released a preview of the DNS services (Finally!) Which allow us to manage DNS zones from within Azure. Which is something that their competition Amazon has had for quite some time. Now since this in preview it is only able to manage it from PowerShell. After speaking with the PM for the product, I also heard that some of the capabilities that will come is

  • Integration with Traffic Manager (Think of the GSLB capabilities!)
  • DNSSEC support
  • Management via the Azure portal
  • Merge with the Office365 capabilities as well (Since you can add your own domain there)

Now everyone can sign up for the preview via

Important to remember that using this service means that the Azure Nameservers become authoritative for your domain. But before we do that we need to register our domain at a registrar first and then delegate the NS to Azure (ill show you how to do that later.

Now to get started, in order to be able to try out Azure DNS you need to be using the resourcemanager cmdlets.

Switch-AzureMode -Name AzureResourceManager

Now we have done this we have access to the DNS cmdlets. The DNS service requires a resource group first so we need to create one. Use the

New-AzureResourceGroup –Name Something –location “Somewhere” might be “west us” for instance.


Then we have to add the network provider by running the command Register-AzureProvider –ProviderNameSpace Microsoft.Network

Next we add the DNS provider to the cmdlets. Register-AzureProviderFeature –ProviderNamespace Microsoft.Network –FeatureName azurednspreview


Now that we have registrered we can create a DNS zone within the resource group.

By running the commands New-AzureDNSZone –name –ResourceGroupName something


If we now get information about the Zone we can also get the nameserver information we need to be able to move the NS at our registrar. By default when creating a zone it does as always create a SOA and NS record. So when we need to add a record to the zone.


Get-AzureDNSRecorSet –ZoneName domainname –Name www –RecordType A –resourcegroup myazureresourcegroup Add-AzureDNSRecordConfig –Ipv4Address “” | Set-AzureDNSRecordSet

and voila!

I can now see that my A record is added to my domain zone


Now since I havent moved my DNS zone I can only verify this by doing a nslookup directly to the Azure DNS servers. And we are good to go!

What new at Ignite! Nano Server, Containers, Azure Stack, OMS, ATA and so on

So this is my recap on what has happend at Ignite, sorted by subject of course but the focus and strategy at Microsoft is clear! “MOVE TO OUR CLOUD” of course they did not leave out the guys on the floor as well.

Microsoft announced numerous changes to their Azure platform, including more of an architechtural change to their IaaS platform (Which is due time) so to sum up Azure changes happening over the last two weeks.

  • User defined routes (Which allow us finally define a routing table for each subnet)
  • Reserved IP addresses (Allow us to move reserved IP addresses between services now!)
  • Instance level public IP
  • Multiple VIPs per Cloud Service
  • Azure DNS (Which allows us to manage our DNS zones from Azure, whic also will eventually support DNSSEC and integrate with Traffic Manager)
  • Networking support for resource manager
  • Bring in BGP routes if you are using ExpressRoute
  • 16 vNICs pr virtual machine
  • Azure Automation with support for Graphical Authoring and integration with on-premises
  • Azure Resource Manager which will allos us to build total services based upon JSON files, this will also play a huge role in Azure Stack
  • IP forwarding on virtual appliances
  • Announced a bunch of different virtual appliance partners which will arrive in the marketplace soon (For instance Citrix Netscaler, CheckPoint and so on)
  • Role Based Access
  • Exchange supported on Premium Storage in Azure

So as you can see there is much on Azure happening, specifically on networking which has been lacking for quite some time. So what about Office365 and EMS?

  • Sway (Will be available to all later this month)
  • New Office2016 Public Preview
  • Skype for Buisness Broadcast meetings
  • Announced one Sync client for OneDrive
  • Mobile offline files IOS and Android OneDrive
  • Save to OneDrive from OWA
  • 20,000 file limit and 10GB max file site will be gone
  • You can see more about the OneDrive Roadmap here
  • Intune announced support for Mac OSX
  • Intune app wrapping for Android
  • Support for Apple Volume Purchage Program
  • Support for MAM in Outlook app
  • Multi-identity
  • Restrict Access to Outlook based upon compliance of device
  • Windows 10 support for Intune
  • Document Tracking with Azure RMS
  • Cloud App Discovery GA
  • Priviliged Identity Managment
  • Also heard that eventually Intune will merge into Azure Active Directory

Other then these news Microsoft also announced a new bundle which is called OMS (Operations Management Suite) which consists of

  • Azure Automation
  • Azure Backup
  • Azure Site Recovery
  • Azure Operational Insights ( Which will later get support for components like networking logging, syslog tracking and CMDB options.

This suite can be tried now! Microsoft also announced that they will be opening for partners to add their own intelligence packs for their own monitoring solutions. Which means that more data moving to the cloud.

So what did Microsoft annonunce for the guys on the floor ? Well alot! For instance a lot of new capabiliteis in Server 2016.

  • Microsoft Advanced Threat Analytics (Which is currently in preview is a combination of networking and log based monitoring to be able to detect attacks like Pass the Hash, accounts that have been comprimised and so on) This will become more advanced with capabilities like networking monitoring and be able to take action if there is an attack.
  • PowerShell DSC support for Linux (Which just came out of nowhere!)
  • Nano Server (Which is a newly created fashin of Windows Server, which is designed for delivering the next generation cloud services with a very low footprint in terms of RAM, DISK and CPU where Microsoft stripped most of the tradisional solutions away. ill be writing more about Nano Server but it essence it now looks more like ESX.
  • Containers, Containers, Containers! (Also something I will be writing more about)
  • Storage Spaced Direct (Shared Nothing File Cluster can also be combined with Hyper-V to deliver HCI)
  • Storage Replica which is not like DFS-R.. Which allow us to Async or Syncronous replicate any volume.
  • Storage QoS on a scale out file server
  • Windows Defender not installed and enabled by default (even i Nano)
  • Rolling Cluster Upgrades
  • RDS support for OpenGL 4.4, OpenCL 1.1 + Support for GEN2 VMs and RemoteFX,
  • Web Application Proxy, preauth for HTTP Basic, HTTP to HTTPS redirect
  • Windows Server 2016 will support VXLAN
  • Software loadbalancing capabilities
  • Production Checkpoints and integration with VSS
  • Linux SecureBoot
  • Connected Standby
  • Hyper-V manager and alternate Credetials
  • ReFS more used in centralized SOFS
  • Binary virtual machine configuration VMCX
  • Hot Add and remove of memory and network adapters
  • SMB 3.1.1 (Pre authentication integrity check, encryption improvements,
  • The Network Controller which will allow central management of virtual and physical network devices
  • Shielded VMs and Host Guardian Service
  • JEA (Just Enough Administration
  • Converged NIC across tenant and RDMA traffic
  • Server Side Support for HTTP/2 including header compression and connecrtion multiplexing on IIS
  • Online Resizing support for Shared VDHX
  • PowerShell Direct to a virtual machine.

Now with all these capabilities in place in the fabric, there is only missing one thing. Which is something they announced in the Keynote which is Azure Stack, now Microsoft means buisness. They are moving in and competing with the likes of OpenStack and Cloudplatform and so on. Now many wondered if this was the new version of Azure Pack ( and it its! its the evolution of Azure Pack) Microsoft will continue to support Azure Pack for a while but the main development will be into Azure Stack. Now unlike Azure Pack, Stack is not so deeply dependant on System Center. Now of course you would still use this to manage the infrastructure, but the fabric connection between Azure Stack Providers would be against Hyper-V or clusters.

The Azure Stack will consist of an Azure like fabric controller and will also have the option to communicate with the network controller to manage the fysical and virtual network layer. Stack will also look and feel like the new portal which is currently in use in the preview portal and will come with a set of different provides to deliver specific services.

With the support of VXLAN in the fabric and some support for Vmware with DPM maybe Microsoft is moving with the Azure Stack and support for Vmware ?

Time will tell, and stay tuned for more.

Live at Keynote Microsoft Ignite

even thou the Wireless Isnt completely reliable I will try to maintain the flow as much as I canm, even thou it might get published later. (I will have to be honest the Wifi is horrible) they havent planned properly, (Cisco based)…

The keynote hall opened around 8 AM, and on the stage Microsoft even had a in-house DJ playing @joeysnow

Now the keynote starts at 9AM, wiere there is expected alot of new stuff to be released. Some of the news will just be recap on what happend at @MSbuild and also just some stuff around.

Just got confirmed that there are 23.000 atendees present at MSIgnite and they are live streaming all of the sessions live! (The keynote hall has 15.000 seats)

First announcement from Satya:

Windows Update for Business. Whch he didnt say so much about. (Technet blog on it here — )

Office2016 new public preview

Skyoe for Buisness broadcasting

Office Delve Organizational analytics.

Windows Server and System Center 2016 

Whats new in System Center Configuration Manager on-prem MDM YAY!

SQL Server 2016 (Preview later today), with streach it to Azure)

Azure Stack (A new release of Azure Pack) Public Preview coming this summer.

Operations Management Suite (One consitent IT control plane, in the same lines of Azure EMS)

Advanced Threat Analytics (Microsoft entering the security field again, Which is going to integrated within AD to see authentication logs. (Guessing its going to be like Audit Collector Service in System Center) more info about the EMS part here —


Windows 10 and Device Guard which is a more and better integrated AppLocker.

Outlook MAM enabled, and Skype for buisness enabled MAM is coming in Q3

Data leackage in Windows 10 with integrated file encryption.

Document traching site for Azure RMS. Which gives us the ability to see who has opened specific documents.

Azure AD leaked credential rolling out over the next couple of weeks. With also the om-premise which I will be trying out later today.

Microsoft also announced Azure DNS

So alot of stuff that was announced today looking forward to trying it out.