Overview: Dynamic configuration of security-group membership for Azure Active Directory is available in public preview. Administrators can set rules for groups that are created in Azure Active Directory based on user attributes (such as department and country). This allows members to be automatically added to or removed from a security group. These groups can be used to provide access to applications or cloud resources (such as SharePoint sites and documents) and to assign licenses to members. There is no additional charge for this feature. For more information, please visit Dynamic memberships for groups in Azure AD.
If you are familiar with SharePoint Target Audience or Claims based role and access, this Azure AD dynamic membership for groups is not new to you, this is only a different way to consume but this Azure feature will allow organisation to plan their role-based authentication and authorisation for Azure hosted application which includes PAAS and IAAS, Office 365 hosted application like exchange, sharepoint or dynamic 365 CRM application.
You will be able to create AD group add users dynamically based on their AD attribute like Department, location, business area etc. once you created these AD groups you will be able to use this group to assign permission or target content with in the Azure and office 365 applications.
You can set up a rule for dynamic membership on security groups or Office 365 groups. Nested group memberships aren’t currently supported for group-based assignment to applications.+
Dynamic memberships for groups require an Azure AD Premium license to be assigned to+
- The administrator who manages the rule on a group
- All members of the group
- In the Azure classic portal, select Active Directory, and then open your organization’s directory.
- Select the Groups tab, and then open the group you want to edit.
- Select the Configure tab, select the Advanced rule option, and then enter the advanced rule into the text box.
Containing twenty-four design patterns and ten related guidance topics, this guide articulates the benefit of applying patterns by showing how each piece can fit into the big picture of cloud application architectures. It also discusses the benefits and considerations for each pattern. Most of the patterns have code samples or snippets that show how to implement the patterns using the features of Microsoft Azure. However the majority of topics described in this guide are equally relevant to all kinds of distributed systems, whether hosted on Azure or on other cloud platforms.
Problem: When you access web application with in the SharePoint sever, it keeps on prompting for authentication.
Solution: Disable Loop Back Check
The following step has to be followed to disable the loop back check in SharePoint Servers,
Step 1: Open the Registry Editor (regedit)
Step 2: Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa in registry
Step 3: Create the dword32 for DisableLoopbackCheck
Step 4: modify the value to 1
Recommended Option: Run this power shell command
New-ItemProperty HKLM:\System\CurrentControlSet\Control\Lsa -Name “DisableLoopbackCheck” -value “1” -PropertyType dword
You may have to restart the servers and will have run this from all of your SharePoint servers.
I came to a scenario to migrate the Box content to SharePoint (Office 365). The cost effective solution is the BOX site/folder owners can use the SharePoint Library Open with Explorer features to move the files from Box to SharePoint Online.
If you would like to automate the process for large content, there are many 3rd party Tools are available in market. I explored the skysync http://www.skysync.com/ which is very straight forward to migrate the content from Box to SharePoint or SharePoint to Box.
Skysync software can be used to Sync or Migrate Files between SharePoint, Box, Office 365, Huddle, Dropbox, Network File Systems & more!
Skysync software is available in 3 editions (Pro, Business and Enterprise) , prices and features are different is each model.
It is very easy to setup a new job for sync or migration. The details features can be find here.
This article helps you to install SharePoint Server 2016 (Preview), I am using Azure VM for this demo/article and I will install Single-Server installation of SharePoint Server 2016 with Database server. I am not seeing any major different in this release with respect the Installation.
Note: In this example, I am using SQL server and SharePoint in single VM
- VM 1: Active Directory & DNS
- VM 2: SharePoint and SQL Server – Single Server Farm
- SQL Server 2014 SP1
- SharePoint Server 2016 – Preview
Service Accounts and Permissions
The following article provides information about the administrative and service accounts that you need for an initial SharePoint Server 2016 IT Preview deployment. Additional accounts and permissions are required to fully implement all aspects of a production farm.
The following article describes SharePoint administrative and services account permissions for the following areas: Microsoft SQL Server, the file system, file shares, and registry entries.
The installation phase contain the following procedures,
- SQL Server Installation
- SharePoint Server 2016
SQL Server Installation
The following steps will be followed to install the SQL Server 2014 SP1,
Login to the VM with SharePoint Setup account
Mount the SQL Server ISO file, if you already download the ISO file on the VN where you want to install SharePoint.
Run the SQL Server Setup EXE.
Click the “Installation” tab
Click the “New SQL Server stand-alone installation or add features to an existing installation”
On the Product Key page, enter the valid licence key. Note: If you are using MSDN subscription the key will be included in the ISO file.
The “SQL server feature installation” is selected by default so don’t change since we are trying to setup SQL server for SP 2016.
Please select only the relevant features, since its Dev/Test VM I have selected all features.
Note: Database Engine service is must.
Select Default instance.
Data base Engine Instance( https://msdn.microsoft.com/en-us/library/hh231298.aspx)
Add the SharePoint Setup Account (select Add Current User).
Once SQL server is installed successfully, Start the SharePoint Installation. This SP 2016 installation is not changed much from SP 2013.
SharePoint Server 2016 Installation
The following steps will be followed to install the SharePoint 2016 Pre-requisite,
Run the Pre-requisite EXE using SharePoint Setup Account.
The prerequisites has to be installed first before the installation of SharePoint Server 2016, the prerequisites installation can ask for restart multiple time. Start the prerequisites installation as shown below,
Run the SharePoint Server setup exe, once the Pre-requisite installed successfully.
Enter key “NQTMW-K63MQ-39G6H-B2CH9-FRDWJ” for SharePoint Server 2016 Preview release.
Service Application & Services Configuration Wizard
SharePoint 2016 – Central Administrator
SharePoint Server 2016 IT Preview has been designed, developed, and tested with the Microsoft Software as a Service (SaaS) strategy at its core. Drawing extensively from that experience, SharePoint Server 2016 IT Preview is designed to help you achieve new levels of reliability and performance and empower users while meeting their demands for greater business mobility.
The TechNet library contains articles that describe how to plan for, deploy, and use all the features of SharePoint Server 2016 IT Preview.
- Explore SharePoint Server 2016 IT Preview
- Plan for SharePoint Server 16 IT Preview
- Install and configure SharePoint Server 16 IT Preview
- Technical reference for SharePoint Server 2016 IT Preview