Latest Topics . Here are 3. Ed Bott in Windows 1. Learn how Microsoft ran its own migration. This documentation is archived and is not being maintained. Technical Case Study. If you're considering moving your Share. Point sites to the. Do you trust the. If you decide to go, how will you deal with all. If you're like most. Share. Point sites extensively, and you wonder. Microsoft SQL Server 2005 Standard Edition, Microsoft SQL Server 2005 Express Edition, Microsoft SQL Server 2005 Developer Edition, Microsoft SQL Server 2005. SharePoint to the cloud: Learn how Microsoft ran its own migration Technical Case Study. Ever wondered what’s going on inside the head of a Hanzo main? This video by dopatwo will tell you everything you need to know. If that’s not enough for you, here. Figure 1. The Microsoft IT Office 3. By fall 2. 01. 5, Microsoft migrated 9. Share. Point sites. Today, employees have 1. Technical articles, content and resources for IT Professionals working in Microsoft technologies. OS/2 Warp 4 desktop. This version was released on 25 September 1996. Developer: IBM and Microsoft (v. 1.0 – 1.2) Written in: C, C++ and assembly language. TheINQUIRER publishes daily news, reviews on the latest gadgets and devices, and INQdepth articles for tech buffs and hobbyists. Windows 7 includes a. So what are the various differences between Microsoft Excel versions? This page takes you through the changes that Microsoft made from versions such as 2013, 2010 and. 8, Google will start bugging Gmail users who are still on Chrome version 53 and earlier. The bottom line: Microsoft Office 2010 is a worthy upgrade for businesses and individual users who need professional-level productivity apps, but it will take. ![]() One. Drive for Business. Microsoft has 7. 6,0. Share. Point sites, portals, and Office 3. Understanding our Share. Point situation. Microsoft employees rely on Share. Microsoft Changes Its Tune With Free Version Of Malwarebytes![]() Point, so we in Microsoft. IT asked ourselves the same questions when it came time to move to the cloud. When. we started our migration in 2. Share. Point on- premises team and publishing sites, and 1. My. Sites. So when it was time for us to migrate to the cloud, it was clear it. Rather than tackle migration all at once, we took a measured. Share. Point site owners to consider if they should. If they wanted to migrate their sites, we asked them if they. This gradual approach worked. By fall 2. 01. 5, we had moved 9. Even better, we were able to eliminate 5. Share. Point sites on our company system, cutting. And because Share. Point Online is more. Share. Point, we were able. These are the big migration challenges we faced: Having too many sites: There were far too many sites for us to consider them individually. First, we identified and shut- down sites that were not being used. Then we used a combination of automation and site- owner engagement to migrate sites that employees were actively using and wanted to keep. Trusting the cloud: Like any customer would be, at first we were cautious about moving to the cloud—so we kept our highly secured data on- premises. But once we saw that our migration efforts were working and that we had the expected security controls in place, we began moving all sites to the cloud regardless of their security level. We held a few sites back for regional compliance controls and complexity reasons. Today, we put our most secure sites in the cloud—even sensitive product and financial information. Moving highly customized sites: Share. Point enables companies to build highly customized internal communication portals and business solutions and, like many customers, Microsoft divisions and groups took full advantage of this by building dozens of multi- layered sites to communicate with employees. Moving these sites with their widely varying customizations intact and functional was a major challenge. Governance 1. 01: Get persnickety about the right plan Once you decide to move your Share. Point sites to the cloud. Being precise about. We knew we had a site proliferation challenge—our employees. To address this challenge, we built an internal governance solution, Auto. Sites. If we don't get a response, the site is. Auto. Sites did not eliminate the need for a good governance. We still needed to ask site owners to think very carefully about what. Share. Point sites and to map out who needed access. Figuring this out before migration started was a must. Just as we asked our site owners to consider governance. Here are some of them: Table 1. Tackling governance. Our challenge. What we did. We had 7. 0,0. 00 Share. Point sites to migrate. We had to decide how much of the migration we wanted to control versus how to enable our employees to migrate their sites themselves. We decided to take a mixed approach. We automated as much as possible by building repeatable processes that did most of the work. We also let our employees migrate their sites, which ranged from asking them if they wanted to keep the site, helping them start new sites, working with them on scheduling, and recruiting them to test the new site to make sure it worked properly. One of the first things to do when you move a Share. Point site to the cloud is decide who gets access and at what level. This is a critical step before you begin migration. We built this into the front end of the migration process. If a site owner wanted to migrate a Share. Point team site to the cloud, the site owner had to decide who would have access and at what level. We preserved their permissions as much as possible to minimize the work site owners needed to do. We needed to make sure that we aligned our on- premises security configurations with the cloud to preserve secure access to migrated sites in the ways our site owners intended. Getting this right was crucial to getting owners of sensitive sites to agree to make the move. Most Azure Active Directory (AD) security groups were replicated in the cloud to provide the same user- to- group linkage found on- premises. The exception was domain- calculated groups (groups without fixed membership) that we did not carry forward and had to be remapped. By replicating on- premises security groups and by re- mapping broader calculated groups to cloud equivalents, we preserved the same security access levels as on- premises. One of the main reasons we wanted our employees to move their Share. Point sites to the cloud was to make it easier for them to work anywhere on any device. This meant giving them access even when they were not on the corporate network. It also meant giving them access no matter what device they were using or where they were connecting. If our employees can't use our technology when and how they want to use it, they will use less- secure technologies to get their work done and hide their actions from IT controls. While it may seem counterintuitive, moving our Share. Point sites to the cloud made them more secure. There are many reasons why, but the larger concept is common sense—the cloud is more secure because Microsoft has invested heavily in the cloud. Updating on- premises sites with modern controls would be costly and hard to manage. Examples of how the cloud is more secure. Requiring two- factor authentication to access sites in the cloud. Allowing IT to wipe your device if it is stolen or lost. Providing encryption at rest with rights protection (data is encrypted when you download something and forget about it). Providing encryption in transit (data is encrypted as you move from site to site). All of our employees have to classify data they create or work with in three levels: top- secret high business impact (HBI), moderate business impact (MBI), and low business impact (LBI). Each team had to decide what data to allow in the cloud, and so did we. Initially, we allowed only MBI and LBI data in the cloud. Once Office 3. 65 added encryption at rest and Azure Rights Management Service (RMS) to the cloud, we allowed HBI (top secret) data to be saved in the cloud. Now our highly confidential data sits in the cloud, including financial data that could influence markets if it leaked and sensitive product specifications and plans. Laying a strong migration foundation meant considering everything we could think of ahead of time. We built a governance plan, established our policies for using Share. Point in the cloud, mapped out when to require employees to move their sites to the cloud and when to allow them to stay on- premises, and then we built out how to handle hosting. Choosing what to move. Once we set up our governance plan, we had to decide what. Here are the main types of Share. Point sites we. moved to the cloud: Table 2. Sorting out what to move and where to put. Workload. Where we put it. Why. Companywide internal portals and internal search. All portals move to Office 3. Share. Point publishing portals. Desire for a common intranet experience available where employees need it. Business personal sharing (storing documents in the cloud instead of on PCs)One. Drive for Business, the cloud- based place where employees store their work. Single destination available on any device when employees are ready to work. Group and organization collaboration (how teams store and access shared work)Cloud- based Share. Point team sites and groups. These are the sites that made up most of our migration work. To make team collaboration sites available to employees to access whenever they need, regardless of location or device. Regionally regulated group and organization collaboration. Retained on- premises Share. Point or Office 3. On- premises allows the company to choose the region where to host its sites. Partner collaboration (extranets)Office 3. Share. Point Online team sites with external sharing AND on- premises dedicated extranet. On- premises Share. Point extranet for managing our partner's identity. Sharing with existing individual external accounts can be done on Share. Point Online. By the time we finished our migration, we had moved 9. Share. Point sites to the cloud, including our most. We decided to leave about 7,0. Share. Point sites on- premises. The last 3,0. 00 or so sites were custom portals—sites that were built by. We handled these on a case- by- case basis, which. Fresh start: No migration is the best migration. We encouraged Microsoft employees to think of migration as a. Organizations change over time—new teams are created and new. We decided to allow teams to start building in the cloud. This gave teams time to think about what they. It also had the secondary. To encourage this. We did this for an entire year before migration started and. Share. Point. sites before we even started migration. Most were rebuilt as part of our start. Getting security right was a challenge throughout the. We did not allow high- security sites to be migrated until we proved. We quickly. proved that Share. Point Online is safe, and we now support all levels of. Now, when employees want a new team collaboration space or a. Office 3. 65 unless the employee applies. We also had the challenge of personal spaces to contend. Our employees used My. Site to share social information about themselves. In the lead- up to migration, we let employees know that. My. Site would be retired within four months and gave them instructions on. Sky. Drive Pro/One. Drive for Business. Over time, My. Sites were set to read- only to give employees.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
November 2017
Categories |