Dienstag, 3. Juli 2018

Me and the Microsoft Awards

The Microsoft MVP Award is given on a yearly based to people who are engaged in technology and community. MVPs are independent from Microsoft but they play an important role in explaining and improving the use of Microsoft products and technologies. In 1993 Microsoft introduced the MVP Award. All starts with about 30 people. Today there are more than 3000 MVPs worldwide. You can get more details about the MVP Award here: https://mvp.microsoft.com/

Since 2013 I am an MVP. I start with being an MVP for SharePoint and since the last reorganization I am an MVP for Office Server and Services. Being an MVP means meeting great people all over the world in the community sharing the same passionate about technology and helping others. You cannot buy the MVP award or download braindumps to get it. You get it by working hard and earning the respect of the community and Microsoft.

Since 2018 I am a Microsoft Reginal Director, too. The program is established also in 1993 and is about 150 people word wide. Neither an MVP or a Reginal Director is an Microsoft employee. The difference between the MVP and Regional Director program is that the MVP program is more focused on communities - Regional Directors are more focused on evangelizing the business. Of course, there are more differences in detail. But from my perspective this is one of the most significant. For more details about the Reginal Direct Programm see this page: https://rd.microsoft.com

Both awards have also some topic in common. Both are focusing on giving value to others and keep on discussing actual and future innovations together with Microsoft.

Therefore, I love being an MVP & RD

Best
Nicki

Mittwoch, 27. Juni 2018

What is the Microsoft 365 license package?

From Office 365 to Microsoft 365

As if the topic of licensing in the Microsoft environment is not complex enough, we will now have a license package called Microsoft 365. Microsoft 365 was announced last year at the partner conference in July 2017. The first two versions (Business and Enterprise) were available from the beginning of August 2017.
" A complete, intelligent solution, including Office 365, Windows 10, and Enterprise Mobility + Security, that empowers everyone to be creative and work together, securely." With this claim Microsoft advertises the license package. But what exactly is behind it and why is it interesting for customers?
Microsoft 365 is the logical continuation of the license package SPE (Secure Productive Enterprise). SPE includes Office 365, Windows 10, Enterprise Mobility + Security and on-prem licenses for SharePoint, Exchange and Skype for Business Server. This provides customers in a transition phase or hybrid model with an optimized license package for security and compliance, Office 365 licensing, Windows licensing and on-prem Office Server licenses. Microsoft 365 now offers this combination for customers who already work completely in the cloud with their processes and solutions.

Okay, and why should I care as a customer?

Not only because of GDPR, the topic of data protection and data security is very interesting in these days. Many Office 365 projects have seen the light of day, focusing on functionality, IT and architectural aspects. In the course of the project, the works council, the data protection officer or IT security usually came to the conclusion that a building block was still missing. Since everyone can now access company data from anywhere and with any end device, compliance and security aspects must also be addressed. The functions & features to implement such requirements are of course available with Microsoft services such as Intune, Cloud App Security or the Azure AD Premium Features. However, it quickly becomes clear that these features are not included in a standard Office 365 E1 or F1 license.
The "Wannacry" attack is still in all our memories. This attack on Windows operating systems has not least sharpened the awareness of how important it is to install current Windows patches and to have an up-to-date virus scanner. To address scenarios like this Windows Defender Advanced Threat Protection as part of Windows 10 Enterprise or for example Microsoft Advanced Threat Analytics are also included in Microsoft 365, depending on the license package.
From a business perspective, Microsoft 365 covers the following scenarios (depending on licensing details):
  • Identity and access control
  • Manage mobile devices and apps
  • Protect and encrypt data
  • Protection against cyber attacks
  • Office 365 licensing (SharePoint, Exchange, Skype for Business, Microsoft Teams, Yammer, etc.)
  • Windows 10 Licensing

From a technical point of view, the following products and functions (depending on licensing details) are part of M365:
  • Azure Active Directory (AD) Premium
  • Cloud App Security
  • Microsoft Intune
  • Azure Information Protection
  • Microsoft Advanced Threat Analytics
  • Windows Defender Advanced Threat Protection
  • Windows 10
  • Office 365 Licensing

What do I need to know to use Microsoft 365?

The license package Microsoft 365 is available in different versions. The functions listed above depend in detail on the respective license level. The following table gives an overview:

  • Microsoft 365 Enterprise is suitable for companies with approximately 300 employees or more. This version is available in E3 or E5 and includes Office 365, Windows 10 Enterprise and the EMS features.
  • Microsoft 365 Business is suitable for small and medium-sized businesses. Windows 10 Pro, Office 365 and the EMS functions are included.
  • Microsoft 365 F1 focuses on firstline workers. This version includes Windows 10 Enterprise, Office 365 F1 and EMS.
  • Microsoft 365 Education is intended for schools and universities and is available in A1, AE and A5 versions.
More details can be found on the official Microsoft 365 page, and all products that are part of Microsoft 365 can still be licensed separately.

What will change with the use of Microsoft 365?

Traditionally, even in medium-sized companies a split into Exchange Team, AD Team, SharePoint Team, Client & Server Team, etc. is normal. With Office 365 all departments have to work much more closely. If the extended functions of Microsoft 365 are now added, close coordination with the IT security department, the data protection officer and the works council must be supplemented.
In addition, as part of the IT strategy, this new Microsoft 365-Team, as part of company IT department, must now have knowledge of all the products involved. Microsoft 365-Team needs to know about Intune, Cloud App Security, Windows Defender etc. and their dependencies, interfaces and interaction options. Education and training are a must.

And what do I need to know as a developer?

At first glance, Microsoft 365 seems to be only for the license manager and the IT administrator. That would have been a little too short. Microsoft gave an outlook on the Graph API roadmap at the Build Conference in May 2018. It can be deduced from this that the services involved in Microsoft 365 are also integrated in this API in the future. Already today, the common API for online services such as Exchange, SharePoint, Office 365 Groups and Teams etc. play an important role for developers. The Microsoft Graph API will become the central endpoint for all cloud services.

Freitag, 15. Juni 2018

Azure Information Protection Part III – AIP Scanner

The AIP Scanner is part of the AIP Client download. After you have downloaded and installed the AIP Client you can start the installation and configuration. But bevor we start the installation let’s have a look at some requirements:
  • A Windows Server 2012 R2 or 2016 Server to run the service (For test and demo you can install it on a Win10 machine)
  • A SQL Server 2012+ local or remote instance (Any version from Express or better is supported)
  • Sysadmin role needed to install scanner service
  • Service requires Log on locally right and Log on as a service right
  • AIP Scanner is an AIP Premium P2/EMS E5 feature for more details review this article: https://azure.microsoft.com/en-us/pricing/details/information-protection/ 

A really good steep-by-steep description about install and configure AIP Scanner is done by Kevin McKinnerney and can be found here: https://blogs.technet.microsoft.com/kemckinn/2018/03/23/easy-configuration-of-the-azure-information-protection-scanner/

As you see in Kevins steep-by-steep guide the scanner runs as a service and uses App Authentifiction to connect with the AIP Service. So we do not need to authenticate to use the scanner.
The scanner has two main configurations which we need to configure using PowerShell:
  • Add-AIPScannerRepository or Set-AIPScannerRepository -> it is about the locations and the conditions for this location
  • Set-AIPScannerConfiguration -> it is about what the scanner should do during the scan

Add-AIPScannerRepository

This cmdlet adds a so called data repository to be scanned and creates a profile of settings. For example, you can specify a default label for unlabeled files, and whether to override an existing label or not. We can specify local folders, UNC paths, and SharePoint Server URLs for SharePoint sites and libraries. The scanner can handle more than one data repository. So you can configure a mix of local folders, UNC paths and SharePoint Server URLs with different setting covered by one AIP Scanner installation.
To change this settings we can use: Set-AIPScannerRepository cmdlet. To remove a data repository use: Remove-AIPScannerRepository cmdlet.
Example:
Set-AIPScannerRepository -Path C:\Temp2 -SetDefaultLabel UsePolicyDefault -MatchPolicy On

To review the settings, we can use Get-AIPScannerRepository. As you can see in my example I have configured two repositories with different settings:


Set-AIPScannerConfiguration

Set-AIPScannerConfiguration cmdlet is used to configure settings for the AIP Scanner. These settings include:
  • Discovery mode or applies labels
  • File will be relabeled YES or NO
  • File attributes are changed YES or NO
  • What is logged in the reports
  • Scanner runs once or continuously
  • Justification message used when required
  • Rights Management owner for protected files

Example:
Set-AIPScannerConfiguration -Enforce On -Schedule OneTime -Type Full -DiscoverInformationTypes All

Set-AIPScannerScannedFileTypes


This cmdlet is used to let the scanner know which files types should be scanned.

The cmdlet sets a list of file types to scan or exclude from scanning. To scan all file types, use *. To scan only specific file types use *.<file name extension>. To exclude specific file types from being scanned use -*.<file name extension>. And to reset the list back to default use @().

If no data repository is specified the setup applies to all data repositories that do not have their own list specified.
To get more examples and details review the official documentation: 
https://docs.microsoft.com/en-us/powershell/module/azureinformationprotection/set-aipscannerscannedfiletypes?view=azureipps

Scenarios

The scanner can typically be used for the following scenarios. Reports are stored in this location: %localappdata%\Microsoft\MSIP\Scanner\Reports

Scan for sensitive information types
#Configure data repository:
Add-AIPScannerRepository -Path C:\Temp2

#Configure Scan: Scan for all known sensitive types
Set-AIPScannerConfiguration -Enforce Off -Schedule OneTime  -Type Full -DiscoverInformationTypes All

#Start Scan
Start-Service AIPScanner

Label / Protect files
#Configure data repository:
Add-AIPScannerRepository -Path C:\Temp2 -OverrideLabel On -DefaultLabelId ae7eaeb0-cfdf-4217-a895-32a6b41311d9 -MatchPolicy Off

#Configure Scan: Scan for all knowen sensitive types
Set-AIPScannerConfiguration -Enforce On -Schedule OneTime -ReportLevel Debug -Type Full

#Start Scan
Start-Service AIPScanner

Scan for sensitive information types and labels and protect files that match
#Configure data repository:
Add-AIPScannerRepository -Path C:\Temp2 -OverrideLabel On -MatchPolicy On

#Configure Scan: Scan for all knowen sensitive types
Set-AIPScannerConfiguration -Enforce On -Schedule OneTime  -Type Full -DiscoverInformationTypes All

#Start Scan
Start-Service AIPScanner

Related posts:

Montag, 21. Mai 2018

Azure Information Protection Part II – PowerShell


This article is on overview about the functions and scenarios using PowerShell in the context of Azure Information Protection. Everything in this article is based on the official Microsoft documentation.
Microsoft published a brilliant Admin Guide about using PowerShell with Azure Information Protection containing all details and scenarios: Admin Guide: Using PowerShell with the Azure Information Protection client.

Overview

In Azure Information Protection we can use PowerShell to:
  • Administering Azure Information Protection
  • Configuration for the super user feature
  • Using Azure Information Protection
  • Work with the AIP Scanner

Azure Information Protection knows two PowerShell modules.
  • AADRM: These cmdlets are used to administer the protection service (Azure Rights Management) for Azure Information Protection.
  • AzureInformationProtection: These cmdlets are used to protect files, label files, and get information about files.

First step is to install the AADRM PowerShell module. To do this open PowerShell and use: Install-Module -Name AADRM. For more details and requirements about how to install AADRM PowerShell modules read this article: Installing the AADRM PowerShell module
To get an overview of all cmdlets use: Get-Command -Module AADRM or look at this list: Cmdlets grouped by administration task
The AzureInformationProtection cmdlets are part of the Azure Information Protection client. These cmdlets can be used with Azure Information Protection, the protection service (Azure Rights Management), and Active Directory Rights Management Services (AD RMS).
To get an overview of all cmdlets use: Get-Command -Module AzureInformationProtection

Main scenarios and some examples

We can use PowerShell for AIP for classification and protection. Let’s have a deeper look on some typical scenarios:

Scenario 1: remove protection from files for others using your own account

In this scenario we need PowerShell to configure the “super user feature”. In addition, we need to configure your account to be a super user for Azure Rights Management. To enable the super user feature, use the PowerShell cmdlet Enable-AadrmSuperUserFeature To assign your user or a groups we can use the Add-AadrmSuperUser cmdlet.

To get a complete overview about the super user feature in AIP refer to this official article: Configuring super users for Azure Rights Management and discovery services or data recovery
The super user feature is also needed if we need to index mailboxes for search operations or if DLP solutions. CEG or anti-malware products can also use the super user to inspect files that are protected by AIP.


Scenario 2: protect or unprotect files without user interaction

First step in this scenario is to connect to Azure Rights Management Service by using this cmdlet: Connect-AadrmService. To login enter your Azure Information Protection tenant administrator credentials.
To get an overview about the ARM instants and to verify that the login was successful use: Get-AadrmConfiguration. The result will be something like this for example:
In the next step we will use PowerShell to get a list of all available Labels using this cmdlet: Get-RMSTemplate. In my example it looks like this:
Now we can to several things:
  • Protect a file: Protect-RMSFile -File C:\Test.docx -InPlace -TemplateId e6ee3481-26b9-45g5-b33a-f774escd43b0
  • Protect all files in a folder: Protect-RMSFile -Folder \ServerABC\Docs -InPlace -TemplateId e6ee3481-26b9-45g5-b33a-f774escd43b0
  • Get the status of a file: Get-RMSFileStatus -File \Server1\Documents\TestABC.docx
  • Remove protection: Unprotect-RMSFile C:\testDoc1.docx -InPlace


Related posts:


Donnerstag, 10. Mai 2018

Azure Information Protection Part I – Overview

Azure Information Protection also known as AIP is an Azure solution that helps an organization to classify, label, and protect its content and emails. This can be done automatically by administrators who define rules and conditions, manually by users, or as a combination where users are given recommendations.
The following picture shows the overall solution and components:
  1. Azure Information Protection is a service in Azure
  2. You can download 3 different clients:
    • AzInfoProtection.exe: The client installer
    • AzInfoProtectionScanner: Can be used to classify and protecting documents stored on File Shares and On-Premises SharePoint servers
    • AzInfoProtectionViewer: Is used to open and view protected files
  3. Policies are configured in Azure management portal or with PowerShell. A Policy is assigned to a user or group
  4. PowerShell can be also used work with AIP
  5. Some Office clients and servers offers a native support for AIP
    • Clients: Word, Excel, PowerPoint, Outlook
    • Server: Exchange, SharePoint
  6. Labels are applied to documents and files. A label can contain different permission levels or specify individual usage rights
A very good starting point is the quick start tutorial for Azure Information Protection. In this tutorial you get a perfect overview about the configuration and settings in AIP.
More details can be found on the official Microsoft websites:
The missing piece in the quick start tutorial for Azure Information Protection is an overview about how Policies and Labels work together.

Policies

Policies are hosting administrative setting like for example:
A Policies must be applied to a user or a group and did not contain any permissions.

Labels

A Label contains different permission levels or specify individual usage rights based on this list:
  • View, Open, Read (VIEW)
  • View Rights (VIEWRIGHTSDATA)
  • Edit Content, Edit (DOCEDIT)
  • Save (EDIT)
  • Print (PRINT)
  • Copy (EXTRACT)
  • Reply (REPLY)
  • Reply All (REPLY ALL)
  • Forward (FORWARD)
  • Change Rights (EDITRIGHTSDATA)
  • Save As, Export (EXPORT)
  • Allow Macros (OBJMODEL)
  • Full Control (OWNER)

Protecting content

Depending on his assigned Policies a user can choose between different Labels to protect a document or files.

Related posts