Webinar Recording : https://youtu.be/KpPGnKtftFI
Link to the PPT Slides : https://www.slideshare.net/JayanthiP4/getting-started-with-microsoft-flow/
Webinar Recording : https://youtu.be/KpPGnKtftFI
Link to the PPT Slides : https://www.slideshare.net/JayanthiP4/getting-started-with-microsoft-flow/
Disclaimer: The contents mentioned in this article below describes the current functionality of Microsoft Office 365 Planner and may or may not change in the mere future.
You can read this complete article on HubFly blog site as well where it’s published on two parts from the link given below .
Microsoft Planner is a planning application available on the Microsoft Office 365 platform. Planner enables users and teams to create plans, assemble and assign tasks, share files, communicate and collaborate with other users, and receive progress updates via various means on the Office 365 platform. It makes it easy for your team to create new plans, organize and assign tasks, share files, chat about what you’re working on, and get updates on progress.
With that being said, in this article I’ll be explaining how the email notification works in Microsoft Planner as this has been bit confusing to understand for beginners.
Planner helps to stay on top of your work and you can also receive email notifications from Planner when the below conditions are met.
Although, these are the criteria’s for receiving email notifications, it’s confusing when you see these things in action. So, let me try to go through all the criteria’s here and help you understand how this works as a Plan owner and as a member of a Plan.
Let’s begin with seeing the different ways of creating a Plan in Office 365 Planner first
1. From the Office 365 App launcher:
a) Navigate to the Office 365 App launcher and you can access Planner from there to create a Plan.
b) Once you’re in the Planner hub you can create a Plan by using the New Plan button as shown in the image below.
Note: Creating a Planner would create an Office 365 group on the back-end as a Planner is officially backed up by an Office 365 group.
2.By creating a Team in Microsoft Teams:
When you create a Team in Microsoft Teams, it creates an Office 365 group on the backend and in addition to that it also creates a Plan in Microsoft Planner.
For instance, please check the image below where I’ve created a Team named as “Planner Test” in Microsoft teams and it has created an Office 365 group as well as a Plan in Microsoft Planner.
Corresponding Office 365 group:
Corresponding Plan in Microsoft Planner:
3.By accessing the below URL:
When you access https://tasks.office.com/ it takes you to the below seen sign-in page and you can access Microsoft Planner from here.
Alright, now let’s get into the main agenda of this article. As already described above you would receive email notifications from Microsoft Planner when either one among the below mentioned criteria’s are met.
Now, let’s take a look on all these criteria’s….
As already mentioned above, creating a Planner will create an Office 365 group on the back end and you would get a welcome email to that Office 365 group as show in the email below.
The intent of this Office 365 group from a Planner perspective is to receive email notifications for all the activities that happens in the Plan.
Note: You would receive this welcome email notification even if you’re the one who created the Plan and in addition to that all the members of Plan would receive this welcome email.
2.When you’re added as a plan member:
When you add a member to this plan, even in such case the member would receive this welcome email from the Office 365 group which is tied to that Plan.
Whenever a task is assigned to a member of a plan, an email notification will be sent to the Office 365 group conversation as shown in the image below.
Note: You would receive this notification on the Office 365 group conversation even if the task was not assigned to you and was assigned to a different member.
However, this functionality of receiving email notification for task assignment is turned off by default in the Plan. You need to go click on the ellipsis above then go to Edit Plan –>Check the “Send notifications about task assignment and task completion to the Plan’s conversation feed” as shown in the image below to receive email notifications.
Note: This won’t be checked by default.
Once this option is activated, notifications about task creation, assignment and completion will be sent to the Plans conversation (in the Office 365 group conversation) and not individually for each user. Currently planner does not send e-mail notification directly to the user’s inbox, rather it sends updates about the plan only to the Office 365 groups conversation.
If the user(s) want to receive notifications directly into their inbox, they need to be subscribed to the plan (Open the plan in Planner -> click on ellipses -> click on Follow plan inbox). This feature will allow users to receive email notifications right into their inbox, but keep in mind, that even if a task was assigned to another user, they will still be notified about this. Basically, every notification from the Group conversation will also be sent to the users that are subscribed to the plan. Please check the image below for reference.
Once you’ve clicked on “Follow plan in Inbox” as shown in the image above you will receive the notifications directly in your personal inbox as well as in the Office 365 group conversation as shown in the image below. The follow feature will send the notifications that are incoming to the Office 365 group mailbox, to the personal mailbox as well.
In my personal inbox:
In the Office 365 group conversations:
You can also verify whether you have followed the plan successfully by doing the same step once again as described and this time you will see “Stop following the plan “instead of seeing “Follow the plan” which confirms that you have successfully subscribed to receive personal email notifications as shown in the image below.
Note: If you are the one that assigns the task to someone (even to yourself) you will not receive the notification in your personal email. It is considered unnecessary as you were the one who assigned it so Planner considers that you are already aware of this.
The email notification which you receive in your personal inbox may not be instant and you need wait for some time to receive it. However, that’s not the case for Office 365 group conversations where you would be receiving notifications from Planner instantly.
4.When any plan member adds a comment to a task that you’ve commented on:
So, every time a comment is made by a plan member on a task that you’ve commented on then you would get a notification for that as well.
Email notification for a comment in Office 365 group:
Email notification for a comment in personal inbox:
Note: You can reply to the comment from the Office 365 group conversations /personal inbox itself, but it wouldn’t be reflecting as a “comment” inside the Plan.
5.When the owner of a plan has turned on task activity notifications in a plan that you’re a member:
This option is something that I’ve explained before, where you as an owner of a plan can go to Edit Plan –>Check the “Send notifications about task assignment and task completion to the Plan’s conversation feed” as shown in the image below to receive email notifications.
Note: This won’t be checked by default.
6.When you have checked the Subscribe new members to notifications email option while creating a Plan:
As shown in the image below, you would be get an option which says “Subscribe new members to notifications emails “while creating a plan as shown in the image below.
At the moment this functionality of this feature is not yet functional and hence enabling it will not have any difference. However, the main reason why this feature is visible is because of the upcoming changes that will be implemented in Planner.
This feature will automatically subscribe every new member to the notification emails – basically, they would not need to go and manually “Follow the plan” as I described above. It will already be set as following by default.
If you still want to use this feature, you can do so from the Office 365 Admin centre, by doing the following steps:
5. If you go back to Planner and start adding new members to the Plan, they will already have the “follow plan in inbox” feature set.
Note: Keep in mind that you will still need to have the Notifications set ON from the (i.e. Plan -> Edit plan):
Note: The catch here is, you won’t be able to make the above said changes with your Global admin account if you don’t have Exchange Online license assigned to it. If you attempt to do so, you would end up getting the below seen error.
Also, please be informed that if you’re doing this modification in an Office 365 group which is tied to a Team in Microsoft Teams then there’s no situation where Teams sends a notification to the Office 365 group. It only has notifications within teams, which can be configured in various ways, but none of them goes to the Office 365 group mailbox and this has already been tested
There might be changes in the future (not documented anywhere just yet) but as of now, there is none.
Also, as you probably know there is a “follow this channel” feature available within teams. This feature is not changed by the “subscribe” checkbox from Office 365 admin center.
Thanks for reading this post …. Good luck with Microsoft Planner!!!
Thanks to everyone who attended our event at Microsoft Bangalore last Saturday .
Please find the event album as well as the slides from the link below .
Event Album :_ http://www.c-sharpcorner.com/Photos/Album.aspx?aid=1015
Design and Implement Azure Web Apps by Ayush Rathi:
Understanding the benefits of Azure AD, EM+S and Tips to get prepared for GDPR Compliance by Ravikumar Sathyamurthy :
Overview of Microsoft Teams and DLP by Radhakrishnan Govindan :
Improving your productivity in Office 365 using Microsoft Flow & PowerApps by Jayanthi & Vignesh Ganesan:
Please keep a watch on the link below for all are upcoming events
SharePoint 2016 –The new kid in town. Well I hope you won’t mind when I say that SharePoint 2016 is the new kid in town considering the fact that it has been more than a year since Microsoft has released SharePoint Server 2016 and it has also announced the release of SharePoint Server 2019 a month back at Ignite Conference. However, there’s reason for me to still call SharePoint 2016 as the new kid in town because it still remains to be a cutting-edge platform for many SharePoint professionals out there and I’ve seen many organizations actively working on adapting SharePoint Server 2016 as the modern collaboration platform for their IT workspace.
So, in this article I’m going to help you with some good amount of information that should help you in planning the SharePoint Server 2016 Implementation in your organization. Alright, let’s get started ….
So, these are the topics I’ll be discussing in detail in this article …
The above-mentioned image should give you a detailed overview about the evolution of SharePoint. I personally remember starting my career with SharePoint 2010 6 years back and at that point of time I’ve seen many experienced SharePoint folks really getting excited about the rich and cool UI of SharePoint 2010 and its rich capabilities. It has indeed come a long way since then and has grown very rapidly compared to its competitors and still remains to be the most preferred solution for Enterprise Content Management. As SharePoint grew, the range of problems businesses could solve with SharePoint grew wider, and changes in technology and business models brought customers new problems as well as new opportunities. Microsoft kept investing in SharePoint, creating a well-rounded collaboration platform that meets the needs of businesses and – most importantly – has the ability to grow and adapt when new challenges are presented. So, with that being said, let’s dive bit deeper and see what the latest version of SharePoint on-premises (i.e. SharePoint 2016) has for us and how it can help to enhance our business.
2. Software & Hardware requirements for Implementing SharePoint Server 2016:
Every time Microsoft introduces the next version of any product the software and hardware requirements for implementing that product keeps changing and that remains true for SharePoint 2016 as well. So, what should I have in terms of software and hardware for implementing SharePoint Server 2016? The details are as follows ….
Software Requirements for SharePoint 2016:
3. Pre-requisites for SharePoint 2016:
SharePoint 2016, the prerequisites are almost essentially the same as they were for SharePoint 2013, with one or two differences (e.g. .Net Framework 4.5.2). The following is a list of all the SharePoint 2016 Prerequisites components you need to download if you are doing an offline installation.
Note: If your machine is connected to the internet, the prerequisite installer module of the SharePoint 2016 media will automatically take care of downloading and installation of prerequisites, so you don’t need to manually download them all.
4. Supported browsers for SharePoint 2016:
5. Boundaries and Limits in SharePoint 2016:
6. Hardware Requirements for SharePoint 2016:
7. Hardware Requirements for Min Role Architecture:
Note: I’ll be explaining in detail about the Min Role Architecture later in this article
8. Focus areas of SharePoint Server 2016:
Being a cloud-born on-premises platform, SharePoint 2016 focuses on the above-mentioned areas …
a) Improved User Experiences:
Making decisions faster and keeping in contact are the most critical responsibilities for increasing effectiveness in any organization. Users’ ability to access information while on the go is now a workplace necessity. SharePoint Server 2016 will provide improved mobile access to content, people and applications along with touch-based experiences across devices and screen sizes. It will make file storage and document collaboration more people-centric. And it will also enable improved user experiences and capabilities derived from innovations in Office 365, available either as part of your on-premises deployment or through a hybrid implementation of SharePoint Server 2016 and Office 365. As a result of this, users will be able to quickly discover contextually relevant information and data that is stored across both on-premises and cloud environments powered by Office Graph and Delve.
b) Cloud-Inspired Infrastructure:
SharePoint 2016 is the first on-premises server release representative of our experience running SharePoint at scale in Office 365, bringing Microsoft’s own internal investments to the customer’s datacenter that improve performance, reliability and scale as well as enabling true hybrid scenarios that can enrich the customer’s existing on-premises investments.
In addition, with an improved, simplified user experience and integration with products such as the next release of Windows Server, the next generation of SQL Server, and Exchange Server 2016, SharePoint Server 2016 will simplify end-user training and support for IT.
c) Compliance and Reporting:
Data Loss Prevention (DLP) is non-negotiable, and overexposure to information can have legal and compliance implications. SharePoint Server 2016 will provide a broad array of features and capabilities designed to make certain that sensitive information remains protected with investments in DLP, new scenarios to enable data encryption, and compliance tools that span on-premises servers and Office 365 while providing a balance between enabling user self-service and ensuring content usage adheres to corporate and security policies .This ensure that the privilege you have doesn’t become intrusive to security and compliance .
9.What’s new in SharePoint Server 2016?
Microsoft never fails to excite its customers by releasing many new features in the new release of every product it develops and SharePoint 2016 is no bar for that. The below mentioned image gives a complete overview of all the new features that has been released in SharePoint 2016.
Note: When I say new features, they might be newly introduced with this release of SharePoint or might be the enhanced version of a feature/service application in the previous release.
As you can see in the image above, SharePoint 2016 comes with almost close to 28 new features.
10.What has been deprecated in SharePoint 2016?
Of course, Microsoft removes few features too which was available in the previous versions of SharePoint and the reason for this is because Microsoft keeps listening to its customers through many user voice channels and based on the feedback given by its customers it either deprecates certain features or tries to enhance a specific feature and releases it once again as a new feature in the next new release or through service packs /CU’s etc.
So, listed below are the features that has been deprecated in SharePoint 2016,
11.Migration Approach to SharePoint 2016:
The below mentioned image depicts the Migration approach to SharePoint 2016.
So, the good news is if you’re running SharePoint 2013 you can directly migrate to SharePoint 2016 and the bad news is you can’t directly migrate to SharePoint 2016 if you’re running SharePoint 2010 version in your environment. However, please note that using third party tools like Share Gate and Metalogix you can migrate from SharePoint 2010 to SharePoint 2016 and even from any legacy version to SharePoint 2016.
Note: To upgrade from SharePoint Server 2013 to 2016, minimal build SharePoint Server 2013 SP1 + March 2013 PU, build number (15.0.4481.1005)
Steps to plan the migration:
The below mentioned image should depict the overall upgrade process:
12. Feature Packs in SharePoint 2016:
With SharePoint 2016 the big new is Microsoft won’t be releasing Service Packs anymore, Feature packs would be taking over Service packs from SharePoint 2016 onwards. However, the release cycle for Feature packs differs from Service packs and let’s talk in detail about that.
The below mentioned image should give you a complete overview of the patching cycle for SharePoint 2016.
So, this is what the image says, Microsoft shipped SharePoint 2016 from March 2016 onwards and as per their normal patching cycle every month they would be releasing a Public update (i.e. Cumulative update) and what happens in this process is, in a specific month’s CU Microsoft would roll out all the new features/fixes etc. and that would be called as a Feature Pack. So, unlike the previous version of SharePoint where Microsoft releases all the new features/services in the form of Service Packs such as SP1 & SP2, for SharePoint 2016 it would be Feature Packs. However, the catch here is that, Microsoft won’t be releasing a specific package once in a year as Service packs instead all the new updates/features would be rolled out in a specific month’s CU and that will be called as a Feature Pack
As of now, Microsoft has released two Feature packs (i.e. Feature Pack 1 & Feature Pack 2). So, before we jump in and talk a look at what’s available in these Feature Packs, let’s try to understand what a Feature Pack is all about.
So, what’s a Feature Pack in SharePoint 2016?
Unlike previous versions of SharePoint, release-to-manufacture (RTM) did not define the end of innovation, but the beginning. As Microsoft continued to develop SharePoint Server 2016, they’ve paid close attention to customer feedback, trends in content management, team collaboration, user experiences across devices, and how the cloud can be blended into existing on-premises scenarios in new and compelling ways. Feature Packs allow us to accelerate delivery of cloud-first features to our Software Assurance customers of SharePoint Server 2016 outside of the traditional 2- to 3-year release cadence.
So, to make this simpler to understand, Feature Pack is an innovative step taken by Microsoft to add new features to SharePoint Product line which were not really announced as part of the initial Product release. Earlier a new feature made its way to SharePoint only as part of Product Launch which happened in three years interval. SharePoint Team will now be taking feedbacks and new features will be deployed as feature packs to SharePoint Server at regular intervals. This will keep SharePoint Server updated with new Cloud features introduced in SharePoint Online
Alright, so this covers Part 1 of “Everything you want to know about SharePoint 2016 “. Will see you all soon in part 2 of this article. Stay tuned!!!
Happy SharePointing!!!…Thanks for reading this post and good luck with your SharePoint 2016 implementation
Webinar Recording :_ https://youtu.be/MrPXgFn6TXk
Link to the PPT Slides :_ https://www.slideshare.net/VigneshGanesanMCPMCI/overview-of-microsoft-teams
Please keep checking my blog site for more webinars and useful articles .
Good luck with Microsoft Teams!!!
I guess most of you would have seen this notification on the “Major updates” section on the Message center in the Office 365 admin center . So the big news is , starting from Oct 19th onwards ,Microsoft To-Do would no more be on preview mode and will be generally available for all the Office 365 users .
As we all know , Microsoft To-Do which was introduced on April 2017 comes from the team behind the most famous Wunderlist app, and delivers a smarter, more personal and intuitive way to help people stay organized and get the most out of every day. Powered by Office 365 integration and an intelligent algorithm, this application takes care of simplifying task management and help users achieve more.
Listed below are the license plans which include “Microsoft To-Do” as of now ….
You can turn on Microsoft To-do for your users from the Office 365 admin center by navigating to the licensing portal–> select the user –> select the preference for To Do and then click Save as shown in the image below .
So please plan the roll-out of Microsoft To-do for your end users accordingly …Good luck with Microsoft To-Do !!!
Listed below are the limitations one must be aware of in Microsoft Teams.
Note: These are the current limitations as of now in Microsoft teams and this may or may not be changed by Microsoft in the future.
The default maximum number of teams that an Office 365 tenant can have is currently 500,000.
A team can have 100 owners.
We can create 100 channels in a Team
A user can create 250 teams.
A global admin can create unlimited number of teams.
A team owner can add 999 members to a team.
No, you can’t search for a private team
No, you can’t customize a team if you’re not the owner of it.
There can be 20 members in a private chat, including the user who created the chat.
The maximum number of people in a meeting is 80.
11. How many people can join a Team which is public?
The maximum number of people for a public team is 2500.
12. How do I restrict the creation of Teams for my end users?
Since Microsoft Teams is officially backed up by an Office 365 group, restricting the access to create an Office 365 group will also restrict the creation of a Team in Microsoft Teams. As a result, users won’t be a to see “Add a Team “button in Microsoft Teams.
Please go through this link to know in detail about creating restrictions for Teams :_
13. If I add a user to an Office 365 group which was created as a part of Team will he have access to the Team?
Yes, he will have access and it would take 15 mins for him to gain access to the Team once he has been added to the Office 365 group .However , the SLA for this is 24 hours .
Thanks for reading this post …. Good luck with Microsoft Teams!!!
Please join us for a webinar on Oct 28th ,2017 at 6:00 pm IST on ” Overview of Microsoft Teams in Office 365” .
We’ll be discussing in detail about Microsoft Teams and all it’s new features and functionalities.
Webinar details : _ http://www.c-sharpcorner.com/events/overview-of-microsoft-teams
For many years SharePoint Migration has been a very challenging task for all the SharePoint professionals as it really requires a lot planning, assessment and careful implementation to ensure that the data remains secure and it doesn’t gets missed during the migration.
While the migration between SharePoint on-premises environment is really straight forward where you need to follow the content database detach/attach or content database copy/restore method, that was not the case while migrating the data from on-premises to Office 365 (i.e. SharePoint Online). You had to depend on many third-party tools such as AvePoint, Sharegate and Metalogix etc. to do this and these tools were indeed very costly to afford. Microsoft recently introduced the Migration API that takes advantage of Azure Blob storage which was quite convincing to use but required a lot of manual effort and even using that you couldn’t perform a migration at the site collection level. So, with all these challenges/uncertainties revolving around SharePoint on-premises to SharePoint online migration, Microsoft has announced the release of its own native Migration tool on Ignite last week. This tool is in beta version for now and is available for the public to download and explore from this link below.
The best part about this tool is, it’s free and you don’t need to be a global admin or a SharePoint admin in Office 365 to use this. All you need is a write access to the destination SharePoint Online site collection and you can use this tool to migrate your data.
Alright, now let’s dive bit deeper and see how to make use of this tool and what are the features we get with this tool that can help to streamline the migration process.
How to use the Microsoft SharePoint Migration Tool?
1.To begin with, please use the link below to download and install the Microsoft SharePoint migration tool as shown in the image below.
2.Once done click on “Install “on the next screen as shown in the image below.
3. This should start to download and install the tool as shown in the image below.
4. After downloading and installing the tool, you would get the below screen. Please go ahead and click on next.
5. You would be prompted for your Office 365 credentials, please go ahead and sign-in with your Office 365 username and password.
6. Once done entering your credentials, please click on sign-in as shown in the image below.
7. After you have successfully signed-in to the tool, you would be seeing three options asking where is your source data as shown in the image below.
8. In this example, I wanted to migrate the data from a “File Share” to a “SharePoint Online site” and hence I’m choosing File Share as the source as shown in the image below and it asks me to choose the folder.
9. Once done choosing the file share path, please go ahead and click on next as shown in the image below.
10. So, once you’re done choosing the source path you would be prompted to choose the destination SharePoint site as shown in the image below. Please specify the site URL and also the document library to where you need to move your content.
Note: Please make sure that you have site collection admin access to the target site because only then it would retrieve the document libraries in the drop-down
11. Once done adding both the source and destination, please go ahead and click on add and the tool will add this to the list of tasks as shown in the image below.
12. So as shown in the image below, you can see the list of tasks added for migration and if required you can add few more tasks as well.
Note: The tasks that you add here can be of different types (meaning, you can add a task for migrating contents from a file share to a SharePoint Online site and the second one can be to migrate data from a SharePoint on-premises site to a SharePoint Online site and the third one can be a bulk migration task using a CSV file)
14. Once you click on the “Migrate” button you can notice that the migration process has started as shown in the image below.
15. Finally, once the migration is completed you can check the completion status as shown in the image below. In addition to that you can also click on the “Open report” button to get the migration reports.
16. Once you click on the “Open report” button the windows explorer will open the below mentioned folder structure from where you can access the migration reports.
17. This is how the contents in the report would look like.
19. So in the above example I showed you how to perform a migration using this tool from a file share to a SharePoint online site. Similarly, you can do the same for migrating the files from a SharePoint on-premises site to a SharePoint online site. However, before doing so please check and ensure that you have site collection access on both the source and destination. Finally, you can plan bulk migration tasks using the CSV file option. I’ll discuss in detail about that in a different article very soon .
What happens behind the scenes while using the Microsoft SharePoint Migration Tool?
Well, just in case if you’re interested to know what happens behind the screen while using the tool the steps below should give you an overview about that.
On a high level this is what happens,
Let’s dig bit further and see what happens at each stage …
On the Authentication stage:
After opening the tool, the first thing we must do is authenticate to the destination SPO site (i.e. the tenant where you will be migrating your files) by providing your username and password .By doing so the tool associates the migration jobs with your account. This allows you to resume your migration from another computer if needed by logging in with the same credentials. This account should be a site collection administrator of the destination where you want to migrate the files.
On the Scanning stage:
Once you click on the “Migrate” button, a scan is performed on every file. Please note that a scan is always performed; even if you elect to not migrate your files (see Advanced Settings). The scan verifies that there is access to the data source and write access to the SharePoint Online destination. It also scans the file for known potential issues and risks.
On the packaging stage:
On the packaging stage, a content package is created that contains a manifest consisting of 8 XMLs.
On the uploading stage:
On the uploading stage, the content package is uploaded to Azure with the manifest. Before a migration job can be accepted from a SPO provided Azure container, the data is encrypted at rest using the AES CBC 256 standard. The files are encrypted along with the manifest files.
On the importing stage:
On the importing stage, the key is provided to SPO SAS. Only Azure and SPO are interacting to fetch and migrate the content into the destination. This process is a timer job based, but does not prevent other jobs from being queued up. During the import, a report is created in the working folder and live updates are made. After the migration job is completed, the log is stored in the Azure container and a final report is created. A log is stored in each Manifest Container.
Recommendations for using the Microsoft SharePoint Migration Tool:
For best performance:
|CPU||64-bit Quad core processor or better|
|Local Storage||SSD : 150 GB free space|
|Network card||1 Gps|
|Operating System||Windows Server 2012 R2 or Windows 10 client
.NET Framework 4.6.2
For slow performance:
|CPU||64-bit 1.4 GHz 2-core processor or better|
|Local Storage||Hard disk: 150 GB free space|
|Network card||High speed internet connection|
|Operating System||Windows Server 2008 R2, Windows 7 updated or better
.NET Framework 4.6.2
Impact on the file permissions when it’s migrated:
The user permission would be retained to the cloud provided that the user accounts are synced to Azure AD using AAD Connect tool and the users have SharePoint Online licenses assigned to them.
The below mentioned table should give you an overview about how the user permissions are mapped when a user is synced to Azure AD and when he/she is not synced:
|User sync status||File Share||SharePoint on-prem files|
|User mapped between on-premises and SPO (using AAD Connect tool or a user mapping file provided)||There are only two types of permissions that will be migrated; Read and Write.
If a file has Write permission for user1, then the file will be set to Contribute for user1 in SPO. If a file has Read permission for user1, then the file will be set to Read for user1 in SPO.
Note: At this time, the special permissions, such as Deny, will not be saved.
|All the unique permissions on a file will be migrated to SPO. Inherited permissions will not be migrated.|
|No user mapping (not-synced, no user mapping file)||Files will be assigned the default permission of the location to which it has been migrated in SPO.||Files will be assigned the default permission of the location to which it has been migrated in SPO.|
Behavior of the tool when you choose SharePoint on-premises and File Share:
SharePoint on-premises: If you select the SharePoint on-premises option, you will be asked to enter the name of the SharePoint Server site where your files are located and prompted for your credentials for that site. You will indicate what document library you wish to migrate.
Note: As of now the tool only supports SharePoint 2013
File Share: If you select the File share option, you will be asked to enter the location of the file share, the URL of the SharePoint Online site and document library where they will be moved.
Advanced settings in the Microsoft SharePoint Migration Tool:
Use the advanced settings option in the tool you can perform the below mentioned tasks as well.
In order to make use of the “Advanced settings” option on the SharePoint Migration Tool, please make use of the gear icon on the window where you see the “Migrate” button after specifying the source and destination as shown in the image below.
|Only perform scanning||If you wish to scan the files as a pre-assessment to migration, turn Only perform scanning on.|
|Enable incremental migration||By setting enable incremental migration to On, it lets you rerun the migration jobs at a later date, migrating only the changes or additions since the previous run.
Important: If you wish to be able to submit this job again for incremental migration, this setting must be set to On before the initial migration job is submitted.
|Migrate file version history||If set to No, only the most recent version of the file will be migrated. If set to Yes, you can choose whether to keep all versions, or limit it to a specific number.|
|Do not migrate hidden files||If set to On, hidden system files will not be migrated.|
|Do not migrate files created before||If you choose to limit what files are migration based on creation date, set your values in this section. This may be to limit the number of files migrated or to adhere to overall company governance policy regarding file retention.|
|Do not migrate files modified before||If you choose to limit what files are migration based on modified date, set your values in this section. This may be to limit the number of files migrated or to adhere to overall company governance policy regarding file retention.|
|Do not migrate files with these extensions||To prevent certain file types from migrating, list each extension, separating it with a vertical bar. For example, mp4|avi|mkv. Do not include the leading “.” before the extension name|
|Do not migrate files and folders with invalid characters||By default, the setting is set to Off. This is the recommended setting. The tool will attempt to move all the files without filtering on characters. If any file can’t be accepted into SPO, a failure message will be generated for that file.
If set to On, the tool will skip any potential special characters. While this can improve performance when the source potentially contains a high number of files containing invalid characters, it also has drawbacks. To prevent malicious activities, source packages that generate more than 100 errors to the destination server will be blocked. As a result, all valid files in that package would also be blocked.
|Active Azure Directory lookup||By default, this is set to On. If no User mapping file is provided by the user, then Active Azure Directory is used as the default for user mapping.|
|Preserve user permissions||By default, this is set to On. If set to Off, no permissions will be preserved.|
|User mapping file||By default, Azure AD lookup is used to map users when submitting migration jobs. If you wish to use your own mapping file, select the file to be used by clicking Choose file. If you choose to use a custom user mapping file and you want to preserve user permissions, turn off Active Azure Directory lookup. By doing so if a user isn’t found in the mapping file, the tool won’t look in up in AAD.|
|SharePoint Migration Tool work folder||By default, a temp folder will be created. If you wish to specify a specific working folder, enter the name here.|
|Use custom Azure storage||If you wish to use your own Azure storage, set this value to On.
If you choose to turn on, additional fields will display to enter your account and key, and settings to select if you want to enable or disable encryption, and whether temporary files are deleted when migration is complete.
The Microsoft SharePoint Migration tool in indeed a powerful and free to use tool. As of now the product is in beta version and Microsoft is continuously working on enhancing the tool by adding many cool features which you normally get to see on any third party migration tool such as Sharegate , Metalogix or AvePoint . You can even plan a migration of terabytes of data by using this tool so that your users can start taking advantage of the cool features in cloud. Last but not least, given the features and simplicity of this tool, this is definitely a must have tool for every SharePoint Admin out there.
You can also read this article on the Hubfly blog site too by going through the link below and very soon I’ll be making a demo video on the Microsoft SharePoint migration tool which would be avaialble on the Hubfly blogsite .
Please subscribe to the Hubfly blogsite for many cool articles on SharePoint & Office 365 .
Good luck with the Microsoft SharePoint Migration Tool….Happy SharePointing!!!
I’m not sure how many of you had the chance to take a look at the Message center in the Office 365 admin center last week , if you haven’t yet I would urge you all to take a look at this announcement which was made on Sep 25th about Microsoft removing the Visio web access/Visio web part and communicate the same to your end users/business .
Although ,it’s too early to talk about this change as the change will come into effect only from Sep 30,2018 onwards I think it would be worthwhile to start preparing ourselves for this change as the Visio web part has been one of the most heavily used web part by many SharePoint users for many years and with this change we should start thinking about at alternative now .