Updates from: 07/03/2021 03:11:47
Service Microsoft Docs article Related commit history on GitHub Change details
SharePoint Prepare IE11 https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/live/SharePoint/SharePointOnline/Prepare-IE11.md
search.appverid:
- MET150 - M365-collaboration
-description: "Prepare your SharePoint environment for the retirement of Internet Explorer 11 for Microsoft 365 apps and services."
+description: "Prepare your SharePoint and OneDrive environment for when Microsoft 365 apps and services stop supporting Internet Explorer 11."
# Prepare your SharePoint environment for the retirement of Internet Explorer 11 for Microsoft 365 apps and services
As Microsoft 365 evolves, we continually evaluate our apps and services to make
Although support for Internet Explorer 11 continues, weΓÇÖve shifted web browser development resources to the [Microsoft Edge browser](https://www.microsoft.com/edge/business). Focusing on Microsoft Edge helps us accelerate innovation in Microsoft 365 experiences from the browser and in modern apps, such as Microsoft Teams, OneDrive, SharePoint, Lists, and more.
-Beginning on August 17, 2021, [Microsoft 365 apps and services will no longer support Internet Explorer 11](/lifecycle/announcements/internet-explorer-11-support-end-dates). While we know this change will be difficult for some customers, we believe that you'll get the most out of Microsoft 365 when using Microsoft Edge. To avoid disruptions, weΓÇÖve identified considerations and practices for admins as you transition off classic SharePoint features that rely on Internet Explorer 11.
+Beginning on August 17, 2021, [Microsoft 365 apps and services will no longer support Internet Explorer 11](/lifecycle/announcements/internet-explorer-11-support-end-dates). While we know this change will be difficult for some customers, we believe that you'll get the most out of Microsoft 365 when using Microsoft Edge. To avoid disruptions, weΓÇÖve identified considerations and practices for admins as you transition off SharePoint features that rely on Internet Explorer 11.
## Deploy a modern browser such as Microsoft Edge
For customers who want guidance on how to plan, deploy, or adopt Microsoft Edge,
And for customers who prefer to get started on their own, we have [self-guided deployment and configuration materials](/deployedge/) on our Docs site, complete with a [series from Microsoft Mechanics](https://www.youtube.com/playlist?list=PLXtHYVsvn_b-uXh1tMeYpT-0iD8tD3tFy).
-## Use sync instead of Open with Explorer
+## Use sync instead of Open with Explorer or View in File Explorer
-[Open with Explorer](https://support.microsoft.com/office/66b574bb-08b4-46b6-a6a0-435fd98194cc) relies on Internet Explorer 11 and isnΓÇÖt available in newer browsers like Microsoft Edge. We recommend using the OneDrive sync app to [sync SharePoint files with your computer](https://support.microsoft.com/office/6de9ede8-5b6e-4503-80b2-6190f3354a88), rather than using Open with Explorer.
+The [Open with Explorer and View in File Explorer](https://support.microsoft.com/office/66b574bb-08b4-46b6-a6a0-435fd98194cc) commands rely on Internet Explorer 11 and aren't available in newer browsers. We recommend using the OneDrive sync app to [sync SharePoint files with your computer](https://support.microsoft.com/office/6de9ede8-5b6e-4503-80b2-6190f3354a88), rather than using Open with Explorer or View in File Explorer.
Sync with [OneDrive Files On-Demand](https://support.microsoft.com/office/0e6860d3-d9f3-4971-b321-7092438fb38e) helps you work with all your cloud files in File Explorer without having to download all the files and use storage space on your device. For easy access to files that people share with you or that you find in SharePoint or Teams, you can [add shortcuts to shared folders](https://support.microsoft.com/office/d66b1347-99b7-4470-9360-ffc048d35a33). The shortcuts then appear in your OneDrive so you can find and work with the files.
To get started deploying and configuring OneDrive in your environment and migrat
- Versions of Windows that don't support [Files On-Demand](https://support.microsoft.com/office/0e6860d3-d9f3-4971-b321-7092438fb38e). Files On-Demand requires Windows 10 Fall Creators Update (version 1709 or later) or Windows Server 2019. However, selective sync can be used as a workaround. > [!NOTE]
-> We understand that some customers may continue to use Open with Explorer to access document libraries. To avoid disruption, these customers will be able to use this feature for a limited time in the classic experience when they go to a document library in Internet Explorer 11. We encourage all customers to move to OneDrive sync for a better user experience and easier access to files.
+> We understand that some customers may continue to use Open with Explorer and View in File Explorer to access document libraries. To avoid disruption, these customers will be able to use these features when they go to a document library in Internet Explorer 11. These features remain in maintenance mode and aren't receiving further development. We encourage all customers to move to OneDrive sync for a better user experience and easier access to files.
## Use Power Apps to automate business processes
SharePoint Deploy File Collaboration https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/live/SharePoint/SharePointOnline/deploy-file-collaboration.md
For detailed information, see [What is Conditional Access?](/azure/active-direct
**Real-time monitoring with alerts**
-Microsoft Cloud App Security provides an extensive policy infrastructure that you can use to monitor activity that you consider to be risky for your organization's data.
+[Microsoft 365 Defender](/microsoft-365/security/defender/microsoft-365-defender) services provide an extensive policy infrastructure that you can use to monitor activity that you consider to be risky for your organization's data.
Examples include:
Examples include:
- Raise an alert when an externally shared file hasn't been updated for a specified period of time.
-Cloud App Security can also watch for anomalous behavior such as unusually large uploads or downloads, access from unusual locations, or unusual admin activity.
+Microsoft 365 Defender can also watch for anomalous behavior such as unusually large uploads or downloads, access from unusual locations, or unusual admin activity.
-By configuring alerts in Cloud App Security, you can be more confident in allowing an open sharing experience for your users.
+By configuring alerts, you can be more confident in allowing an open sharing experience for your users.
You can see the alerts on the [Microsoft 365 Defender alerts page](https://security.microsoft.com/alerts).
-For detailed information about Cloud App Security, see [Microsoft Cloud App Security overview](/cloud-app-security/what-is-cloud-app-security).
+For detailed information about alerts in Microsoft 365 Defender, see [Investigate alerts in Microsoft 365 Defender](/microsoft-365/security/defender/investigate-alerts).
**Monitoring with reports**
SharePoint Differences Classic Modern Search https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/live/SharePoint/SharePointOnline/differences-classic-modern-search.md
SharePoint in Microsoft 365 has both a classic and a modern search experience. M
As a search admin, you canΓÇÖt enable or disable either search experience, both are enabled by default. Users get the classic search experience on publishing sites, classic team sites, and in the Search Center. Users get the Microsoft Search experience on the SharePoint start page, hub sites, communication sites, and modern team sites. [Learn about classic and modern sites](https://support.office.com/article/5725c103-505d-4a6e-9350-300d3ec7d73f)
-The most visible difference is that the Microsoft Search box is placed at the top of the SharePoint, in the header bar. Another difference is that Microsoft Search is personal. The results you see are different from what other people see, even when you search for the same words. You'll see results before you start typing in the search box, based on your previous activity and trending content in Microsoft 365, and the results update as you type. [Learn more about the Microsoft Search experience for users](https://support.office.com/article/d5ed5d11-9e5d-4f1d-b8b4-3d371fe0cb87)ΓÇï.
+The most visible difference is that the Microsoft Search box is placed at the top of the SharePoint, in the header bar. Another difference is that Microsoft Search is personal. The results you see are different from what other people see, even when you search for the same words. You'll see results before you start typing in the search box, based on your previous activity and trending content in Microsoft 365, and the results update as you type. [Learn more about the Microsoft Search experience for users](https://support.office.com/article/d5ed5d11-9e5d-4f1d-b8b4-3d371fe0cb87).
-ΓÇïSearch admin can customize the *classic* search experience, but not the Microsoft Search experience. As a search admin you can *tailor* Microsoft Search to your organization so it's easy for your users to find often needed content in your organization.
+Search admin can customize the *classic* search experience, but not the Microsoft Search experience. As a search admin you can *tailor* Microsoft Search to your organization so it's easy for your users to find often needed content in your organization.
You use the SharePoint admin center to manage classic search and the Microsoft 365 admin center to manage Microsoft Search. Certain aspects of the classic search settings also impact the modern search experience: - The [search schema](manage-search-schema.md) determines how content is collected in and retrieved from the search index. Because both search experiences use the same search index to find search results, any changes you make to the search schema, apply to both experiences. The Microsoft Search experience doesn't support changing the sort order of results or building refiners based on metadata. Therefore, the following search schema settings donΓÇÖt affect the Microsoft Search experience:
- - Sortable
- - Refinable
- - Company name extraction (to be deprecated as of November 15th, 2019)
+ - Sortable
+ - Refinable
+ - Company name extraction (to be deprecated as of November 15th, 2019)
- The modern search experience only shows results from the default result source. If you change the default [result source](manage-result-sources.md), both search experiences are impacted. - Depending on the search scenario, some Microsoft Search features might not work if the [classic global Search Center URL](./specify-default-search-center.md) is not set to point to the URL of the default classic Search Center. Depending on your tenant, this URL is "yourcompanyname.sharepoint.com/search" or "yourcompanyname.sharepoint.com/search/pages". Furthermore, ensure that the Search Center site collection exists and that all users have read access to it. - If you temporarily [remove a search result](remove-search-results.md), the result is removed in both search experiences.-- The classic search experience lets admins define **promoted results** to help users find important content, while the Microsoft Search experience uses **bookmarks** to achieve the same. When you [create a promoted result](../SharePointServer/search/manage-query-rules.md) at the organization level, users might also see it on the **All** tab on the Microsoft Search results page if they searched across the whole organization. For example, when users search from the search box on a hub site, they're only searching in the sites associated with the hub and therefore they don't see any promoted results even if they are on the **All** tab. But when users search from the SharePoint start page, they might see promoted results on the **All** tab. If you have defined both a promoted result and a bookmark for the same content (same URL), only the bookmark will appear on the **All** tab.
+- The classic search experience lets admins define **promoted results** to help users find important content, while the Microsoft Search experience uses **bookmarks** to achieve the same. When you [create a promoted result](../SharePointServer/search/manage-query-rules.md) at the organization level, users might also see it on the **All** tab on the Microsoft Search results page if they searched across the whole organization. For example, when users search from the search box on a hub site, they're only searching in the sites associated with the hub and therefore they don't see any promoted results even if they are on the **All** tab. But when users search from the SharePoint start page, they might see promoted results on the **All** tab. If you have defined both a promoted result and a bookmark for the same content (same URL), only the bookmark will appear on the **All** tab.
SharePoint Hide App Tiles On App Launcher https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/live/SharePoint/SharePointOnline/hide-app-tiles-on-app-launcher.md
description: "See how to show or hide links to Sites or OneDrive."
# Hide the OneDrive and SharePoint app tiles
-By default, the OneDrive and SharePoint app tiles appear in the app launcher and on the Microsoft 365 admin centerΓÇï. If your subscription doesn't include one of these services, or if you don't want users using one of them, you can hide the app tile for it.
+By default, the OneDrive and SharePoint app tiles appear in the app launcher and on the Microsoft 365 admin center. If your subscription doesn't include one of these services, or if you don't want users using one of them, you can hide the app tile for it.
![Microsoft 365 start page with SharePoint selected](media/4ff2c093-2b26-4d28-a65b-4d02e66818df.png)
By default, the OneDrive and SharePoint app tiles appear in the app launcher and
1. Go to the [Settings page of the new SharePoint admin center](https://admin.microsoft.com/sharepoint?page=settings&modern=true), and sign in with an account that has [admin permissions](./sharepoint-admin-role.md) for your organization.
->[!NOTE]
->If you have Office 365 Germany, [sign in to the Microsoft 365 admin center](https://go.microsoft.com/fwlink/p/?linkid=848041), then browse to the SharePoint admin center and open the Settings page. <br>If you have Office 365 operated by 21Vianet (China), [sign in to the Microsoft 365 admin center](https://go.microsoft.com/fwlink/p/?linkid=850627), then browse to the SharePoint admin center and open the Settings page.
+ > [!NOTE]
+ > If you have Office 365 Germany, [sign in to the Microsoft 365 admin center](https://go.microsoft.com/fwlink/p/?linkid=848041), then browse to the SharePoint admin center and open the Settings page. <br>If you have Office 365 operated by 21Vianet (China), [sign in to the Microsoft 365 admin center](https://go.microsoft.com/fwlink/p/?linkid=850627), then browse to the SharePoint admin center and open the Settings page.
2. At the bottom of the page, select **classic settings page**.
-
+ 3. In **Show or Hide App Tiles**, select the tile you want to hide.
-
+ ![Show or Hide App Tiles settings](media/516f0f56-c44e-465e-8ec5-ba56fbbe2b3b.png) > [!NOTE]
By default, the OneDrive and SharePoint app tiles appear in the app launcher and
[Customize the Microsoft 365 theme for your organization](/office365/admin/setup/customize-your-organization-theme)
-[Add custom tiles to the app launcher](/office365/admin/manage/customize-the-app-launcher)
+[Add custom tiles to the app launcher](/office365/admin/manage/customize-the-app-launcher)
SharePoint Information Architecture Models Examples https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/live/SharePoint/SharePointOnline/information-architecture-models-examples.md
How to get started
Moving to modern navigation from classic SharePoint navigation is a process that depends on the size of your organization and the complexity of your tenantΓÇÖs configuration. Below are general guidelines and tools you can use to get started: - Define new intranet [business objectives](./plan-intranet.md#identify-initiatives) and [choose pilot scenarios](./plan-intranet.md#choose-pilot-scenarios)-- Learn about [user needs](./information-architecture-modern-experience.md#understand-your-content) and find methods to [test potential designs](https://www.nngroup.com/articles/quantitative-user-research-methods/)
+- [Get organized](./information-architecture-principles.md#get-organized) and find methods to [test potential designs](https://www.nngroup.com/articles/quantitative-user-research-methods/)
- Take an inventory of your current sites and subsites - Start [planning hubs](./planning-hub-sites.md) and your [home site](./home-site.md) by grouping high priority tasks and content - Release hubs and associated sites in phases
SharePoint Intranet Governance https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/live/SharePoint/SharePointOnline/intranet-governance.md
description: "Planning intranet governance"
As you plan your new intranet project, think about how youΓÇÖll govern the site architecture and the content. Your intranet governance plan should be created in the context of the overall governance plan for Microsoft 365. As a key business solution in your digital workplace, your intranet will have its own unique governance requirements and expectations, especially because of its organization-wide focus and impact.
-Planning intranet governance should happen during the [envisioning process](./intranet-overview.md#envision) - to ensure that all stakeholders have shared vision and goals. Envisioning is only the beginning. Your intranet governance plan will evolve as your organization evolves and as new capabilities are added to SharePoint and Microsoft 365.
+Planning intranet governance should happen during the [exploration phase](./intranet-overview.md#explore) - to ensure that all stakeholders have shared vision and goals. Envisioning is only the beginning. Your intranet governance plan will evolve as your organization evolves and as new capabilities are added to SharePoint and Microsoft 365.
A good governance plan helps define the priorities for the intranet and helps to prevent content sprawl. It also ensures that roles and responsibilities are clearly defined and communicated ΓÇô and ideally, incorporated into job descriptions or performance goals. One aspect that often separates your intranet from other solutions is the number of people who are involved in creating and maintaining content. To ensure ongoing success, it is important to make sure that each of your intranet stakeholders and users understand their roles and responsibilities.
Each organization will have its own set of policies and guidelines. General topi
### Site provisioning and decommissioning
-A key intranet governance decision involves determining who can create a new intranet site. Your modern [intranet architecture will be ΓÇ£flatΓÇ¥](./information-architecture-modern-experience.md#guiding-principle--the-world-is-flat) which means that your intranet will contain many sites. Do you want to provide a self-service model for new intranet sites or do you want to manage site creation through a form submission and workflow? There is no right answer to this question ΓÇô but no matter which approach you choose, you need to think about governance. There are two popular solutions to governing new site creation:
+
+A key intranet governance decision involves determining who can create a new intranet site. Your modern [intranet architecture will be ΓÇ£flatΓÇ¥](./information-architecture-modern-experience.md#guiding-principle-the-world-is-flat) which means that your intranet will contain many sites. Do you want to provide a self-service model for new intranet sites or do you want to manage site creation through a form submission and workflow? There is no right answer to this question ΓÇô but no matter which approach you choose, you need to think about governance. There are two popular solutions to governing new site creation:
#### Implement a site request process for intranet sites
SharePoint Plan Implement Navigation Design https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/live/SharePoint/SharePointOnline/plan-implement-navigation-design.md
Information architecture includes five primary elements:
|Plan |Build |Manage | | - | - | - |
-|1. Ensure you understand your [users needs and the site goals](./information-architecture-modern-experience.md#understand-your-users) <br>2. Learn about designing for [local navigation](./plan-navigation-modern-experience.md#local-navigation) |1. Customize the [navigation](https://support.microsoft.com/office/customize-the-navigation-on-your-sharepoint-site-3cd61ae7-a9ed-4e1e-bf6d-4655f0bf25ca) of your site <br>2. Consider [joining a hub site](https://support.microsoft.com/office/associate-a-sharepoint-site-with-a-hub-site-ae0009fd-af04-4d3d-917d-88edb43efc05) to increase viewership <br>3. Target [navigational links](https://support.microsoft.com/office/target-navigation-news-and-files-to-specific-audiences-33d84cb6-14ed-4e53-a426-74c38ea32293) to specific audiences |1. Use [site analytics](https://support.microsoft.com/office/view-usage-data-for-your-sharepoint-site-2fa8ddc2-c4b3-4268-8d26-a772dc55779e) to understand how users are engaging with your site <br>2. Review site navigation as needed to ensure all links are active, relevant, and up to date|
+|1. Ensure you understand your [users needs and the site goals](./information-architecture-modern-experience.md#understand-your-role-and-how-to-collaborate). <br>2. Learn about designing for [local navigation](./information-architecture-modern-experience.md#local-navigation). |1. Customize the [navigation](https://support.microsoft.com/office/customize-the-navigation-on-your-sharepoint-site-3cd61ae7-a9ed-4e1e-bf6d-4655f0bf25ca) of your site. <br>2. Consider [joining a hub site](https://support.microsoft.com/office/associate-a-sharepoint-site-with-a-hub-site-ae0009fd-af04-4d3d-917d-88edb43efc05) to increase viewership. <br>3. Target [navigational links](https://support.microsoft.com/office/target-navigation-news-and-files-to-specific-audiences-33d84cb6-14ed-4e53-a426-74c38ea32293) to specific audiences. |1. Use [site analytics](https://support.microsoft.com/office/view-usage-data-for-your-sharepoint-site-2fa8ddc2-c4b3-4268-8d26-a772dc55779e) to understand how users are engaging with your site. <br>2. Review site navigation as needed to ensure all links are active, relevant, and up to date.|
**New navigational design for a hub:**
Information architecture includes five primary elements:
|Plan |Build |Manage | | - | - | - |
-|1. Ensure you understand your [users needs and the site goals](./information-architecture-modern-experience.md#understand-your-users) <br>2. Learn about designing for [global navigation](./plan-navigation-modern-experience.md#global-navigation) <br>3. Consider using a [hub site](./planning-hub-sites.md) to group similar sites together <br>4. Learn about [multi-lingual](./plan-navigation-modern-experience.md#multilingual-considerations) considerations |1. Decide on a [menu style](./plan-navigation-modern-experience.md#navigation-menus-in-sharepoint) <br>2. Customize the [navigation](https://support.microsoft.com/office/customize-the-navigation-on-your-sharepoint-site-3cd61ae7-a9ed-4e1e-bf6d-4655f0bf25ca) for individual sites <br>3. Set up [associations and permissions for hub sites](https://support.microsoft.com/office/set-up-your-sharepoint-hub-site-e2daed64-658c-4462-aeaf-7d1a92eba098) |1. Use [hub analytics](https://support.microsoft.com/office/view-usage-data-for-your-sharepoint-site-2fa8ddc2-c4b3-4268-8d26-a772dc55779e) to understand how users are engaging with your site <br>2. Review site navigation as needed to ensure all links are active, relevant, and up to date |
+|1. Ensure you understand your [users needs and the site goals](./information-architecture-modern-experience.md#understand-your-role-and-how-to-collaborate). <br>2. Learn about designing for [global navigation](./information-architecture-modern-experience.md#global-navigation). <br>3. Consider using a [hub site](./planning-hub-sites.md) to group similar sites together. <br>4. Learn about [multi-lingual](https://support.microsoft.com/office/create-multilingual-communication-sites-pages-and-news-2bb7d610-5453-41c6-a0e8-6f40b3ed750c) considerations. |1. Decide on a [menu style](./plan-navigation-modern-experience.md#navigation-menus-in-sharepoint). <br>2. Customize the [navigation](https://support.microsoft.com/office/customize-the-navigation-on-your-sharepoint-site-3cd61ae7-a9ed-4e1e-bf6d-4655f0bf25ca) for individual sites. <br>3. Set up [associations and permissions for hub sites](https://support.microsoft.com/office/set-up-your-sharepoint-hub-site-e2daed64-658c-4462-aeaf-7d1a92eba098). |1. Use [hub analytics](https://support.microsoft.com/office/view-usage-data-for-your-sharepoint-site-2fa8ddc2-c4b3-4268-8d26-a772dc55779e) to understand how users are engaging with your site. <br>2. Review site navigation as needed to ensure all links are active, relevant, and up to date. |
**New navigational design for an intranet site:**
Information architecture includes five primary elements:
|Plan |Build |Manage | | - | - | - |
-|1. Define new intranet [business objectives](./plan-intranet.md#identify-initiatives) and choose [pilot scenarios](./plan-intranet.md#choose-pilot-scenarios) <br>2. Learn about [user needs](./information-architecture-modern-experience.md#understand-your-content) and find methods to [test potential designs](https://www.nngroup.com/articles/quantitative-user-research-methods/) <br>3. Take an inventory of your current sites and subsites <br>4. Plan the [home site](./home-site.md) |1. Start [planning hubs](./planning-hub-sites.md) and your [home site](./home-site.md) by grouping high priority tasks and content <br>2. Set up [associations and permissions for hub sites](https://support.microsoft.com/office/set-up-your-sharepoint-hub-site-e2daed64-658c-4462-aeaf-7d1a92eba098) <br>3. Release hubs and associated sites in phases |1. Establish an intranet review team that ensures navigation and content are up to date and aligned with your organization <br>2. Regularly review [hub and site analytics](https://support.microsoft.com/office/view-usage-data-for-your-sharepoint-site-2fa8ddc2-c4b3-4268-8d26-a772dc55779e) to track page traffic and popular content <br>3. Make navigation changes based on your learning from user testing and analytics |
+|1. Define new intranet [business objectives](./plan-intranet.md#identify-initiatives) and choose [pilot scenarios](./plan-intranet.md#choose-pilot-scenarios). <br>2. Learn about [user needs](./information-architecture-principles.md#get-organized) and find methods to [test potential designs](https://www.nngroup.com/articles/quantitative-user-research-methods/). <br>3. Take an inventory of your current sites and subsites <br>4. Plan the [home site](./home-site.md). |1. Start [planning hubs](./planning-hub-sites.md) and your [home site](./home-site.md) by grouping high priority tasks and content. <br>2. Set up [associations and permissions for hub sites](https://support.microsoft.com/office/set-up-your-sharepoint-hub-site-e2daed64-658c-4462-aeaf-7d1a92eba098). <br>3. Release hubs and associated sites in phases. |1. Establish an intranet review team that ensures navigation and content are up to date and aligned with your organization. <br>2. Regularly review [hub and site analytics](https://support.microsoft.com/office/view-usage-data-for-your-sharepoint-site-2fa8ddc2-c4b3-4268-8d26-a772dc55779e) to track page traffic and popular content. <br>3. Make navigation changes based on your learning from user testing and analytics. |
-[**Next: learn how to get started planning and implementing SharePoint site navigation**](plan-navigation-modern-experience.md)
+[**Next: learn how to get started planning and implementing SharePoint site navigation**](plan-navigation-modern-experience.md)
SharePoint Sharepoint 2013 Dev Test Environments In Azure https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/live/SharePoint/SharePointServer/administration/sharepoint-2013-dev-test-environments-in-azure.md
In this procedure, you download copies of the basic SharePoint 2013 farm templat
Create a local folder to store the ARM template files for the basic SharePoint 2013 farm. Fill in the **$myFolder** variable value (removing the text and the "<" and ">" characters between the quotes) and run the following commands from Azure PowerShell:
-```
+```powershell
$myFolder="<your local folder path, such as C:\azure\templates\BasicSPFarm>" $url1="https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/sharepoint-three-vm/azuredeploy.json" $url2="https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/sharepoint-three-vm/azuredeploy.parameters.json"
$webclient.DownloadFile($url2,$filePath)
Ensure that the download was successful with this command.
-```
+```powershell
dir $myFolder ```
Modify the **azuredeploy.json** file as needed for your basic SharePoint 2013 fa
Next, sign in to Azure PowerShell.
-```
+```powershell
Connect-AzAccount ``` Determine the Azure subscription for the basic SharePoint farm with this command.
-```
+```powershell
Get-AzSubscription | Sort SubscriptionName | Select SubscriptionName ``` Set your subscription to the correct one with these commands.
-```
+```powershell
$subscrName="<subscription name>" Select-AzSubscription -SubscriptionName $subscrName ``` Next, specify the resource group name and Azure location for the deployment with these commands.
-```
+```powershell
$rgName="<resource group name>" $locName="<Azure location, such as West US>" ``` You can get a list of existing resource groups with this command.
-```
+```powershell
Get-AzResourceGroup | Sort ResourceGroupName | Select ResourceGroupName ```
If needed, create a new resource group.
> [!NOTE] > If you are using an existing resource group, the resources and settings of the template can impact the resources within the group. You should perform a careful analysis of the existing resources of the resource group to ensure that do not overlap in an undesirable way.
-```
+```powershell
New-AzResourceGroup -Name $rgName -Location $locName ```
Next, determine the following values, for which you may be prompted when you exe
- sharePointFarmPassphrasePassword -- spDNSPrefix: ![](../media/TableLine.png)
+- spDNSPrefix: ![A blank line that represents the DNS label for the SharePoint server's public IP address](../media/TableLine.png)
This value is the DNS label for the SharePoint server's public IP address, which hosts the first site collection and the Central Administration site. -- sppublicIPAddressName: ![](../media/TableLine.png)
+- sppublicIPAddressName: ![A blank line that represents the DNS host name for the public IP address of the ARM resource](../media/TableLine.png)
The DNS host name for the public IP address of the ARM resource. -- storageAccountNamePrefix: ![](../media/TableLine.png)
+- storageAccountNamePrefix: ![A blank line that represents the prefix for storage names](../media/TableLine.png)
The name must be between 3 and 24 characters in length and use numbers and lower-case letters only. Example: contosotestsp2013farm. Use these commands to specify a deployment name and execute the template **without** the azuredeploy.parameters.json file:
-```
+```powershell
$deployName="<deployment name>" New-AzResourceGroupDeployment -Name $deployName -ResourceGroupName $rgName -TemplateFile $myFolder\azuredeploy.json ``` Use these commands to specify a deployment name and execute the template **with** the azuredeploy.parameters.json file:
-```
+```powershell
$deployName="<deployment name>" New-AzResourceGroupDeployment -Name $deployName -ResourceGroupName $rgName -TemplateFile $myFolder\azuredeploy.json -TemplateParameterFile $myFolder\azuredeploy.parameters.json ```
In this procedure, you download copies of the high-availability SharePoint 2013
Create a local folder to store the ARM template files for the high-availability SharePoint 2013 farm. Fill in the **$myFolder** variable value (removing the text and the "<" and ">" characters between the quotes) and run the following commands from Azure PowerShell:
-```
+```powershell
$myFolder="<your local folder path, such as C:\azure\templates\HASPFarm>" $url1=https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/sharepoint-server-farm-ha/azuredeploy.json" $url2="https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/sharepoint-server-farm-ha/azuredeploy.parameters.json"
$webclient.DownloadFile($url2,$filePath)
Ensure that the download was successful with this command.
-```
+```powershell
dir $myFolder ```
Modify the **azuredeploy.json** file as needed for your high-availability ShareP
Next, sign in to Azure PowerShell.
-```
+```powershell
Connect-AzAccount ``` Determine the Azure subscription for the high-availability SharePoint farm with this command.
-```
+```powershell
Get-AzSubscription | Sort SubscriptionName | Select SubscriptionName ``` Set your subscription to the correct one with these commands.
-```
+```powershell
$subscrName="<subscription name>" Select-AzSubscription -SubscriptionName $subscrName ``` Next, specify the resource group name and Azure location for the deployment with these commands.
-```
+```powershell
$rgName="<resource group name>" $locName="<Azure location, such as West US>" ``` You can get a list of existing resource groups with this command.
-```
+```powershell
Get-AzResourceGroup | Sort ResourceGroupName | Select ResourceGroupName ```
If needed, create a new resource group.
> [!NOTE] > If you are using an existing resource group, the resources and settings of the template can impact the resources within the group. You should perform a careful analysis of the existing resources of the resource group to ensure that do not overlap in an undesirable way.
-```
+```powershell
New-AzResourceGroup -Name $rgName -Location $locName ```
Next, determine the following values, for which you may be prompted when you exe
- sharePointFarmPassphrasePassword -- spDNSPrefix: ![](../media/TableLine.png)
+- spDNSPrefix: ![A blank line that represents the DNS label](../media/TableLine.png)
This value is the DNS label for the SharePoint server's public IP address, which hosts the first site collection and the Central Administration site. -- sppublicIPAddressName: ![](../media/TableLine.png)
+- sppublicIPAddressName: ![A blank line that represents the DNS host name](../media/TableLine.png)
The DNS host name for the public IP address of the ARM resource. -- storageAccountNamePrefix: ![](../media/TableLine.png)
+- storageAccountNamePrefix: ![A blank line that represents the prefix for names of storage accounts](../media/TableLine.png)
The name must be between 3 and 24 characters in length and *use numbers and lower-case letters only* . Example: contosotestsp2013farm. Use these commands to specify a deployment name and execute the template **without** the azuredeploy.parameters.json file:
-```
+```powershell
$deployName="<deployment name>" New-AzResourceGroupDeployment -Name $deployName -ResourceGroupName $rgName -TemplateFile $myFolder\azuredeploy.json ``` Use these commands to specify a deployment name and execute the template **with** the azuredeploy.parameters.json file:
-```
+```powershell
$deployName="<deployment name>" New-AzResourceGroupDeployment -Name $deployName -ResourceGroupName $rgName -TemplateFile $myFolder\azuredeploy.json -TemplateParameterFile $myFolder\azuredeploy.parameters.json ```
SharePoint Sharepoint Intranet Farm In Azure Phase 1 Configure Azure https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/live/SharePoint/SharePointServer/administration/sharepoint-intranet-farm-in-azure-phase-1-configure-azure.md
Last updated 03/15/2019
audience: ITPro f1.keywords: - CSH-+ ms.prod: sharepoint-server-itpro localization_priority: Normal
Azure must be provisioned with these basic components for networking and storage
Before you begin configuring Azure components, fill in the following tables. To assist you in the procedures for configuring Azure, print this section and write down the needed information or copy this section to a document and fill it in. For the settings of the Azure virtual network (VNet), fill in Table V.
-|**Item**|**Configuration setting**|**Description**|**Value**|
+| Item | Configuration setting | Description | Value |
|:--|:--|:--|:--|
-|1. <br/> |VNet name <br/> |A name to assign to the Azure Virtual Network (example SPFarmNet). <br/> |![](../media/TableLine.png) <br/> |
-|2. <br/> |VNet location <br/> |The Azure datacenter that will contain the virtual network. <br/> |![](../media/TableLine.png) <br/> |
-|3. <br/> |VPN device IP address <br/> |The public IPv4 address of your VPN device's interface on the Internet. <br/> |![](../media/TableLine.png) <br/> |
-|4. <br/> |VNet address space <br/> |The address space for the virtual network. Work with your IT department to determine this address space. <br/> |![](../media/TableLine.png) <br/> |
-|5. <br/> |IPsec shared key <br/> |A 32-character random, alphanumeric string that will be used to authenticate both sides of the site-to-site VPN connection. Work with your IT or security department to determine this key value. Alternately, see [Create a random string for an IPsec preshared key](https://social.technet.microsoft.com/wiki/contents/articles/32330.create-a-random-string-for-an-ipsec-preshared-key.aspx). <br/> |![](../media/TableLine.png) <br/> |
+|1. |VNet name |A name to assign to the Azure Virtual Network (example SPFarmNet). | :::image type="icon" source="../media/TableLine.png"::: |
+|2. |VNet location |The Azure datacenter that will contain the virtual network. | :::image type="icon" source="../media/TableLine.png"::: |
+|3. |VPN device IP address |The public IPv4 address of your VPN device's interface on the Internet. | :::image type="icon" source="../media/TableLine.png"::: |
+|4. |VNet address space |The address space for the virtual network. Work with your IT department to determine this address space. | :::image type="icon" source="../media/TableLine.png"::: |
+|5. |IPsec shared key |A 32-character random, alphanumeric string that will be used to authenticate both sides of the site-to-site VPN connection. Work with your IT or security department to determine this key value. Alternately, see [Create a random string for an IPsec preshared key](https://social.technet.microsoft.com/wiki/contents/articles/32330.create-a-random-string-for-an-ipsec-preshared-key.aspx). | :::image type="icon" source="../media/TableLine.png"::: |
**Table V: Cross-premises virtual network configuration**
See [Address space calculator for Azure gateway subnets](https://gallery.technet
Work with your IT department to determine these address spaces from the virtual network address space.
-|**Item**|**Subnet name**|**Subnet address space**|**Purpose**|
+| Item | Subnet name | Subnet address space | Purpose |
|:--|:--|:--|:--|
-|1. <br/> |![](../media/TableLine.png) <br/> |![](../media/TableLine.png) <br/> |The subnet used by the Windows Server Active Directory (AD) VMs. <br/> |
-|2. <br/> |![](../media/TableLine.png) <br/> |![](../media/TableLine.png) <br/> |The subnet used by the VMs in the SQL Server cluster. <br/> |
-|3. <br/> |![](../media/TableLine.png) <br/> |![](../media/TableLine.png) <br/> |The subnet used by the SharePoint app and search servers. <br/> |
-|4. <br/> |![](../media/TableLine.png) <br/> |![](../media/TableLine.png) <br/> |The subnet used by the front end and distributed cache servers. <br/> |
-|5. <br/> |GatewaySubnet <br/> |![](../media/TableLine.png) <br/> |The subnet used by the Azure gateway virtual machines. <br/> |
+|1. | :::image type="icon" source="../media/TableLine.png"::: | :::image type="icon" source="../media/TableLine.png"::: |The subnet used by the Windows Server Active Directory (AD) VMs. |
+|2. | :::image type="icon" source="../media/TableLine.png"::: | :::image type="icon" source="../media/TableLine.png"::: |The subnet used by the VMs in the SQL Server cluster. |
+|3. | :::image type="icon" source="../media/TableLine.png"::: | :::image type="icon" source="../media/TableLine.png"::: |The subnet used by the SharePoint app and search servers. |
+|4. | :::image type="icon" source="../media/TableLine.png"::: | :::image type="icon" source="../media/TableLine.png"::: |The subnet used by the front end and distributed cache servers. |
+|5. |GatewaySubnet | :::image type="icon" source="../media/TableLine.png"::: |The subnet used by the Azure gateway virtual machines. |
**Table S: Subnets in the virtual network** Next, fill in Table I for the static IP addresses assigned to virtual machines and load balancer instances.
-|**Item**|**Purpose**|**IP address on the subnet**|**Value**|
+| Item | Purpose | IP address on the subnet | Value |
|:--|:--|:--|:--|
-|1. <br/> |Static IP address of the first domain controller <br/> |The fourth possible IP address for the address space of the subnet defined in Item 1 of Table S. <br/> |![](../media/TableLine.png) <br/> |
-|2. <br/> |Static IP address of the second domain controller <br/> |The fifth possible IP address for the address space of the subnet defined in Item 1 of Table S. <br/> |![](../media/TableLine.png) <br/> |
-|3. <br/> |Static IP address of the internal load balancer for the front end and distributed cache SharePoint servers <br/> |The sixth possible IP address for the address space of the subnet defined in Item 4 of Table S. <br/> |![](../media/TableLine.png) <br/> |
-|4. <br/> |Static IP address of the internal load balancer for the listener address of the SQL server cluster <br/> |The fourth possible IP address for the address space of the subnet defined in Item 2 of Table S. <br/> |![](../media/TableLine.png) <br/> |
-|5. <br/> |Static IP address of the first SQL server <br/> |The fifth possible IP address for the address space of the subnet defined in Item 2 of Table S. <br/> |![](../media/TableLine.png) <br/> |
-|6. <br/> |Static IP address of the second SQL server <br/> |The sixth possible IP address for the address space of the subnet defined in Item 2 of Table S. <br/> |![](../media/TableLine.png) <br/> |
-|7. <br/> |Static IP address of the minority node server <br/> Note that this is not needed if you are using a [cloud witness](/windows-server/failover-clustering/deploy-cloud-witness). <br/> |The seventh possible IP address for the address space of the subnet defined in Item 2 of Table S. <br/> |![](../media/TableLine.png) <br/> |
-|8. <br/> |Static IP address of the first application and search SharePoint server <br/> |The fourth possible IP address for the address space of the subnet defined in Item 3 of Table S. <br/> |![](../media/TableLine.png) <br/> |
-|9. <br/> |Static IP address of the second application and search SharePoint server <br/> |The fifth possible IP address for the address space of the subnet defined in Item 3 of Table S. <br/> |![](../media/TableLine.png) <br/> |
-|10. <br/> |Static IP address of the first front end and distributed cache SharePoint server <br/> |The fourth possible IP address for the address space of the subnet defined in Item 4 of Table S. <br/> |![](../media/TableLine.png) <br/> |
-|11. <br/> |Static IP address of the second front end and distributed cache SharePoint server <br/> |The fifth possible IP address for the address space of the subnet defined in Item 4 of Table S. <br/> |![](../media/TableLine.png) <br/> |
+|1. |Static IP address of the first domain controller |The fourth possible IP address for the address space of the subnet defined in Item 1 of Table S. | :::image type="icon" source="../media/TableLine.png"::: |
+|2. |Static IP address of the second domain controller |The fifth possible IP address for the address space of the subnet defined in Item 1 of Table S. | :::image type="icon" source="../media/TableLine.png"::: |
+|3. |Static IP address of the internal load balancer for the front end and distributed cache SharePoint servers |The sixth possible IP address for the address space of the subnet defined in Item 4 of Table S. | :::image type="icon" source="../media/TableLine.png"::: |
+|4. |Static IP address of the internal load balancer for the listener address of the SQL server cluster |The fourth possible IP address for the address space of the subnet defined in Item 2 of Table S. | :::image type="icon" source="../media/TableLine.png"::: |
+|5. |Static IP address of the first SQL server |The fifth possible IP address for the address space of the subnet defined in Item 2 of Table S. | :::image type="icon" source="../media/TableLine.png"::: |
+|6. |Static IP address of the second SQL server |The sixth possible IP address for the address space of the subnet defined in Item 2 of Table S. | :::image type="icon" source="../media/TableLine.png"::: |
+|7. |Static IP address of the minority node server <br/> Note that this is not needed if you are using a [cloud witness](/windows-server/failover-clustering/deploy-cloud-witness). |The seventh possible IP address for the address space of the subnet defined in Item 2 of Table S. | :::image type="icon" source="../media/TableLine.png"::: |
+|8. |Static IP address of the first application and search SharePoint server |The fourth possible IP address for the address space of the subnet defined in Item 3 of Table S. | :::image type="icon" source="../media/TableLine.png"::: |
+|9. |Static IP address of the second application and search SharePoint server |The fifth possible IP address for the address space of the subnet defined in Item 3 of Table S. | :::image type="icon" source="../media/TableLine.png"::: |
+|10. |Static IP address of the first front end and distributed cache SharePoint server |The fourth possible IP address for the address space of the subnet defined in Item 4 of Table S. | :::image type="icon" source="../media/TableLine.png"::: |
+|11. |Static IP address of the second front end and distributed cache SharePoint server |The fifth possible IP address for the address space of the subnet defined in Item 4 of Table S. | :::image type="icon" source="../media/TableLine.png"::: |
**Table I: Static IP addresses in the virtual network** For the two Domain Name System (DNS) servers in your on-premises network that you want to use when initially setting up the domain controllers in your virtual network, fill in Table D. Note that two blank entries are listed, but you can add more. Work with your IT department to determine this list.
-|**Item**|**DNS server friendly name**|**DNS server IP address**|
+| Item | DNS server friendly name | DNS server IP address |
|:--|:--|:--|
-|1. <br/> |![](../media/TableLine.png) <br/> |![](../media/TableLine.png) <br/> |
-|2. <br/> |![](../media/TableLine.png) <br/> |![](../media/TableLine.png) <br/> |
+|1. | :::image type="icon" source="../media/TableLine.png"::: | :::image type="icon" source="../media/TableLine.png"::: |
+|2. | :::image type="icon" source="../media/TableLine.png"::: | :::image type="icon" source="../media/TableLine.png"::: |
**Table D: On-premises DNS servers**
To route packets from the cross-premises network to your organization network ac
For the set of local network address spaces, fill in Table L. Note that three blank entries are listed but you will typically need more. Work with your IT department to determine this list of address spaces.
-|**Item**|**Local network address space**|
+| Item | Local network address space |
|:--|:--|
-|1. <br/> |![](../media/TableLine.png) <br/> |
-|2. <br/> |![](../media/TableLine.png) <br/> |
-|3. <br/> |![](../media/TableLine.png) <br/> |
+|1. | :::image type="icon" source="../media/TableLine.png"::: |
+|2. | :::image type="icon" source="../media/TableLine.png"::: |
+|3. | :::image type="icon" source="../media/TableLine.png"::: |
**Table L: Address prefixes for the local network**
Now let's begin building the Azure infrastructure to host your SharePoint farm.
First, start an Azure PowerShell prompt and login to your account.
-```
+```powershell
Connect-AzAccount ``` Get your subscription name using the following command.
-```
+```powershell
Get-AzSubscription | Sort Name | Select Name ``` Set your Azure subscription. Replace everything within the quotes, including the \< and \> characters, with the correct name.
-```
+```powershell
$subscr="<subscription name>" Select-AzSubscription -SubscriptionName $subscr ``` Next, create the new resource groups for your intranet SharePoint farm. To determine a unique set of resource group names, use this command to list your existing resource groups.
-```
+```powershell
Get-AzResourceGroup | Sort ResourceGroupName | Select ResourceGroupName ``` Fill in the following table for the set of unique resource group names.
-|**Item**|**Resource group name**|**Purpose**|
+| Item | Resource group name | Purpose |
|:--|:--|:--|
-|1. <br/> |![](../media/TableLine.png) <br/> |Domain controllers <br/> |
-|2. <br/> |![](../media/TableLine.png) <br/> |Database cluster servers <br/> |
-|3. <br/> |![](../media/TableLine.png) <br/> |App and search servers <br/> |
-|4. <br/> |![](../media/TableLine.png) <br/> |Front end and distributed cache servers <br/> |
-|5. <br/> |![](../media/TableLine.png) <br/> |Infrastructure elements <br/> |
+|1. | :::image type="icon" source="../media/TableLine.png"::: |Domain controllers |
+|2. | :::image type="icon" source="../media/TableLine.png"::: |Database cluster servers |
+|3. | :::image type="icon" source="../media/TableLine.png"::: |App and search servers |
+|4. | :::image type="icon" source="../media/TableLine.png"::: |Front end and distributed cache servers |
+|5. | :::image type="icon" source="../media/TableLine.png"::: |Infrastructure elements |
**Table R: Resource groups** Create your new resource groups with these commands.
-```
+```powershell
$locName="<an Azure location, such as West US>" $rgName="<Table R - Item 1 - Name column>" New-AzResourceGroup -Name $rgName -Location $locName
New-AzResourceGroup -Name $rgName -Location $locName
Next, you create the Azure virtual network and its subnets that will host your intranet SharePoint farm.
-```
+```powershell
$rgName="<Table R - Item 5 - Resource group name column>" $locName="<Azure location>" $locShortName="<the location of the resource group in lowercase with spaces removed, example: westus>"
New-AzVirtualNetwork -Name $vnetName -ResourceGroupName $rgName -Location $locNa
Next, you create network security groups for each subnet that contains virtual machines. To perform subnet isolation, you can add rules for the specific types of traffic allowed or denied to the network security group of a subnet.
-```
+```powershell
# Create network security groups $vnet=Get-AzVirtualNetwork -ResourceGroupName $rgName -Name $vnetName New-AzNetworkSecurityGroup -Name $spSubnet1Name -ResourceGroupName $rgName -Location $locShortName
$vnet | Set-AzVirtualNetwork
Next, use these commands to create the gateways for the site-to-site VPN connection.
-```
+```powershell
$rgName="<Table R - Item 5 - Resource group name column>" $locName="<Azure location>" $vnetName="<Table V - Item 1 - Value column>"
$localGateway=New-AzLocalNetworkGateway -Name $localGatewayName -ResourceGroupNa
$vnetConnectionName="SPS2SConnection" $vnetConnectionKey="<Table V - Item 5 - Value column>" $vnetConnection=New-AzVirtualNetworkGatewayConnection -Name $vnetConnectionName -ResourceGroupName $rgName -Location $locName -ConnectionType IPsec -SharedKey $vnetConnectionKey -VirtualNetworkGateway1 $vnetGateway -LocalNetworkGateway2 $localGateway- ``` Next, record the public IPv4 address of the Azure VPN gateway for your virtual network from the display of this command:
-```
+```powershell
Get-AzPublicIpAddress -Name $publicGatewayVipName -ResourceGroupName $rgName ```
Next, ensure that the address space of the virtual network is reachable from you
Next, define the names of four availability sets. Fill out Table A.
-|**Item**|**Purpose**|**Availability set name**|
+| Item | Purpose | Availability set name |
|:--|:--|:--|
-|1. <br/> |Domain controllers <br/> |![](../media/TableLine.png) <br/> |
-|2. <br/> |SQL servers <br/> |![](../media/TableLine.png) <br/> |
-|3. <br/> |Application and search servers <br/> |![](../media/TableLine.png) <br/> |
-|4. <br/> |Front-end and distributed cache servers <br/> |![](../media/TableLine.png) <br/> |
+|1. |Domain controllers | :::image type="icon" source="../media/TableLine.png"::: |
+|2. |SQL servers | :::image type="icon" source="../media/TableLine.png"::: |
+|3. |Application and search servers | :::image type="icon" source="../media/TableLine.png"::: |
+|4. |Front-end and distributed cache servers | :::image type="icon" source="../media/TableLine.png"::: |
**Table A: Availability sets**
You will need these names when you create the virtual machines in phases 2, 3, a
Create your availability sets with these Azure PowerShell commands.
-```
+```powershell
$locName="<the Azure location of your resource group>" $rgName="<Table R - Item 1 - Resource group name column>" $avName="<Table A - Item 1 - Availability set name column>"
Use [SharePoint Intranet Farm in Azure Phase 2: Configure domain controllers](sh
[Designing a SharePoint Server 2016 farm in Azure](./designing-a-sharepoint-server-2016-farm-in-azure.md)
-[Install SharePoint Server](../install/install.md)
+[Install SharePoint Server](../install/install.md)
SharePoint Sharepoint Intranet Farm In Azure Phase 2 Configure Domain Controllers https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/live/SharePoint/SharePointServer/administration/sharepoint-intranet-farm-in-azure-phase-2-configure-domain-controllers.md
Last updated 04/06/2018
audience: ITPro f1.keywords: - CSH-+ ms.prod: sharepoint-server-itpro localization_priority: Normal
You must complete this phase before moving on to [SharePoint Intranet Farm in Az
First, you need to fill out the **Virtual machine name** column of Table M and modify virtual machine sizes as needed in the **Minimum size** column.
-|**Item**|**Virtual machine name**|**Gallery image**|**Minimum size**|**Storage type**|
+| Item | Virtual machine name | Gallery image | Minimum size | Storage type |
|:--|:--|:--|:--|:--|
-|1. <br/> |![](../media/TableLine.png) (first domain controller, example DC1) <br/> |Windows Server 2016 Datacenter <br/> |Standard_D2 <br/> |StandardLRS <br/> |
-|2. <br/> |![](../media/TableLine.png) (second domain controller, example DC2) <br/> |Windows Server 2016 Datacenter <br/> |Standard_D2 <br/> |StandardLRS <br/> |
-|3. <br/> |![](../media/TableLine.png) (first SQL Server computer, example SQL1) <br/> |Microsoft SQL Server 2016 Enterprise - Windows Server 2016 <br/> |Standard_DS4 <br/> |PremiumLRS <br/> |
-|4. <br/> |![](../media/TableLine.png) (second SQL Server computer, example SQL2) <br/> |Microsoft SQL Server 2016 Enterprise - Windows Server 2016 <br/> |Standard_DS4 <br/> |PremiumLRS <br/> |
-|5. <br/> |![](../media/TableLine.png) (majority node witness for the cluster, example MN1) <br/> |Windows Server 2016 Datacenter <br/> |Standard_D2 <br/> |StandardLRS <br/> |
-|6. <br/> |![](../media/TableLine.png) (first SharePoint application and search server, example APP1) <br/> |Microsoft SharePoint Server 2016 Trial - Windows Server 2012 R2 <br/> |Standard_DS4 <br/> |PremiumLRS <br/> |
-|7. <br/> |![](../media/TableLine.png) (second SharePoint application and search server, example APP2) <br/> |Microsoft SharePoint Server 2016 Trial - Windows Server 2012 R2 <br/> |Standard_DS4 <br/> |PremiumLRS <br/> |
-|8. <br/> |![](../media/TableLine.png) (first SharePoint front end and distributed cache server, example WEB1) <br/> |Microsoft SharePoint Server 2016 Trial - Windows Server 2012 R2 <br/> |Standard_DS4 <br/> |PremiumLRS <br/> |
-|9. <br/> |![](../media/TableLine.png) (second SharePoint front end and distributed cache server, example WEB2) <br/> |Microsoft SharePoint Server 2016 Trial - Windows Server 2012 R2 <br/> |Standard_DS4 <br/> |PremiumLRS <br/> |
+|1. <br/> |![Image of a blank line, instance 1](../media/TableLine.png) (first domain controller, example DC1) <br/> |Windows Server 2016 Datacenter <br/> |Standard_D2 <br/> |StandardLRS <br/> |
+|2. <br/> |![Image of a blank line, instance 2](../media/TableLine.png) (second domain controller, example DC2) <br/> |Windows Server 2016 Datacenter <br/> |Standard_D2 <br/> |StandardLRS <br/> |
+|3. <br/> |![Image of a blank line, instance 3](../media/TableLine.png) (first SQL Server computer, example SQL1) <br/> |Microsoft SQL Server 2016 Enterprise - Windows Server 2016 <br/> |Standard_DS4 <br/> |PremiumLRS <br/> |
+|4. <br/> |![Image of a blank line, instance 4](../media/TableLine.png) (second SQL Server computer, example SQL2) <br/> |Microsoft SQL Server 2016 Enterprise - Windows Server 2016 <br/> |Standard_DS4 <br/> |PremiumLRS <br/> |
+|5. <br/> |![Image of a blank line, instance 5](../media/TableLine.png) (majority node witness for the cluster, example MN1) <br/> |Windows Server 2016 Datacenter <br/> |Standard_D2 <br/> |StandardLRS <br/> |
+|6. <br/> |![Image of a blank line, instance 6](../media/TableLine.png) (first SharePoint application and search server, example APP1) <br/> |Microsoft SharePoint Server 2016 Trial - Windows Server 2012 R2 <br/> |Standard_DS4 <br/> |PremiumLRS <br/> |
+|7. <br/> |![Image of a blank line, instance 7](../media/TableLine.png) (second SharePoint application and search server, example APP2) <br/> |Microsoft SharePoint Server 2016 Trial - Windows Server 2012 R2 <br/> |Standard_DS4 <br/> |PremiumLRS <br/> |
+|8. <br/> |![Image of a blank line, instance 8](../media/TableLine.png) (first SharePoint front end and distributed cache server, example WEB1) <br/> |Microsoft SharePoint Server 2016 Trial - Windows Server 2012 R2 <br/> |Standard_DS4 <br/> |PremiumLRS <br/> |
+|9. <br/> |![Image of a blank line, instance 9](../media/TableLine.png) (second SharePoint front end and distributed cache server, example WEB2) <br/> |Microsoft SharePoint Server 2016 Trial - Windows Server 2012 R2 <br/> |Standard_DS4 <br/> |PremiumLRS <br/> |
**Table M - Virtual machines for the SharePoint Server 2016 intranet farm in Azure**
Recall that you defined Tables R, V, S, I, and A in [SharePoint Intranet Farm in
When you have supplied all the correct values, run the resulting block at the Azure PowerShell prompt or in the PowerShell Integrated Script Environment (ISE) on your local computer.
-```
+```powershell
# Set up variables common to both virtual machines $locName="<Azure location of the SharePoint farm>" $vnetName="<Table V - Item 1 - Value column>"
$diskConfig=New-AzDiskConfig -AccountType $diskStorageType -Location $locName -C
$dataDisk1=New-AzDisk -DiskName ($vmName + "-DataDisk1") -Disk $diskConfig -ResourceGroupName $rgName $vm=Add-AzVMDataDisk -VM $vm -Name ($vmName + "-DataDisk1") -CreateOption Attach -ManagedDiskId $dataDisk1.Id -Lun 1 New-AzVM -ResourceGroupName $rgName -Location $locName -VM $vm- ``` > [!NOTE]
Use the remote desktop client of your choice and create a remote desktop connect
Next, you need to add the extra data disk to the first domain controller with these commands from a Windows PowerShell command prompt:
-```
+```powershell
Get-Disk | Where PartitionStyle -eq "RAW" | Initialize-Disk -PartitionStyle MBR -PassThru | New-Partition -AssignDriveLetter -UseMaximumSize | Format-Volume -FileSystem NTFS -NewFileSystemLabel "WSAD Data"- ``` Next, test the first domain controller's connectivity to locations on your organization network by using the **ping** command to ping names and IP addresses of resources on your organization network.
This procedure ensures that DNS name resolution is working correctly (that the v
Next, from the Windows PowerShell command prompt on the first domain controller, run the following commands:
-```
+```powershell
$domname="<DNS domain name of the domain for which this computer will be a domain controller, such as corp.contoso.com>" $cred = Get-Credential -Message "Enter credentials of an account with permission to join a new domain controller to the domain" Install-WindowsFeature AD-Domain-Services -IncludeManagementTools Install-ADDSDomainController -InstallDns -DomainName $domname -DatabasePath "F:\NTDS" -SysvolPath "F:\SYSVOL" -LogPath "F:\Logs" -Credential $cred- ``` You will be prompted to supply the credentials of a domain administrator account. The computer will restart.
Use the remote desktop client of your choice and create a remote desktop connect
Next, you need to add the extra data disk to the second domain controller with these commands from a Windows PowerShell command prompt:
-```
+```powershell
Get-Disk | Where PartitionStyle -eq "RAW" | Initialize-Disk -PartitionStyle MBR -PassThru | New-Partition -AssignDriveLetter -UseMaximumSize | Format-Volume -FileSystem NTFS -NewFileSystemLabel "WSAD Data" ``` Next, run the following commands:
-```
+```powershell
$domname="<DNS domain name of the domain for which this computer will be a domain controller, such as corp.contoso.com>" $cred = Get-Credential -Message "Enter credentials of an account with permission to join a new domain controller to the domain" Install-WindowsFeature AD-Domain-Services -IncludeManagementTools Install-ADDSDomainController -InstallDns -DomainName $domname -DatabasePath "F:\NTDS" -SysvolPath "F:\SYSVOL" -LogPath "F:\Logs" -Credential $cred- ``` You will be prompted to supply the credentials of a domain administrator account. The computer will restart. Next, you need to update the DNS servers for your virtual network so that Azure assigns virtual machines the IP addresses of the two new domain controllers to use as their DNS servers.
-```
+```powershell
$rgName="<Table R - Item 4 - Resource group name column>" $adrgName="<Table R - Item 1 - Resource group name column>" $locName="<your Azure location>"
Note that we restart the two domain controllers so that they are not configured
Next, we need to create an Active Directory replication site to ensure that servers in the Azure virtual network use the local domain controllers. Log on to the primary domain controller with a domain administrator account and run the following commands from an administrator-level Windows PowerShell prompt:
-```
+```powershell
$vnet="<Table V - Item 1 - Value column>" $vnetSpace="<Table V - Item 5 - Value column>" New-ADReplicationSite -Name $vnet New-ADReplicationSubnet -Name $vnetSpace -Site $vnet- ``` ## Configure SharePoint farm accounts and permissions
The SharePoint farm needs the following user accounts:
Log on to any computer with a domain administrator account for the domain for which the domain controllers are members, open an administrator-level Windows PowerShell command prompt, and run these commands *one at a time* :
-```
+```powershell
New-ADUser -SamAccountName sp_farm -AccountPassword (read-host "Set user password" -assecurestring) -name "sp_farm" -enabled $true -PasswordNeverExpires $true -ChangePasswordAtLogon $false ```
-```
+```powershell
New-ADUser -SamAccountName sp_farm_db -AccountPassword (read-host "Set user password" -assecurestring) -name "sp_farm_db" -enabled $true -PasswordNeverExpires $true -ChangePasswordAtLogon $false ```
-```
+```powershell
New-ADUser -SamAccountName sp_install -AccountPassword (read-host "Set user password" -assecurestring) -name "sp_install" -enabled $true -PasswordNeverExpires $true -ChangePasswordAtLogon $false ```
-```
+```powershell
New-ADUser -SamAccountName sqlservice -AccountPassword (read-host "Set user password" -assecurestring) -name "sqlservice" -enabled $true -PasswordNeverExpires $true -ChangePasswordAtLogon $false ```
Use [SharePoint Intranet Farm in Azure Phase 3: Configure SQL Server Infrastruct
[Designing a SharePoint Server 2016 farm in Azure](./designing-a-sharepoint-server-2016-farm-in-azure.md)
-[Install SharePoint Server](../install/install.md)
+[Install SharePoint Server](../install/install.md)
SharePoint Workflow In Sharepoint Server https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/live/SharePoint/SharePointServer/governance/workflow-in-sharepoint-server.md
description: "Workflows in SharePoint allow you to model and automate business p
Workflows in SharePoint allow you to model and automate business processes. These business processes can range from simple to complex. But most importantly, workflow lets users focus on doing the work -- rather than managing the workflow.
-Workflows help people to collaborate on documents and to manage project tasks by implementing business processes on documents and items in a SharePoint site. Workflows help organizations adhere to consistent business processes, and improve organizational efficiency and productivity.
+Workflows help people to collaborate on documents and to manage project tasks by implementing business processes on documents and items in a SharePoint site. Workflows help organizations adhere to consistent business processes, and improve organizational efficiency and productivity.
## SharePoint 2013 Workflow and Power Automate SharePoint Server 2019 supports a variety of workflow technologies to meet the needs of our customers. These workflow technologies are described below.
-* The SharePoint 2013 Workflow platform is the recommended workflow technology for SharePoint Server 2019. These workflows integrate with Microsoft Workflow Manager and will provide a stable and reliable workflow experience for SharePoint Server 2019.ΓÇï
+
+* The SharePoint 2013 Workflow platform is the recommended workflow technology for SharePoint Server 2019. These workflows integrate with Microsoft Workflow Manager and will provide a stable and reliable workflow experience for SharePoint Server 2019.
* Power Automate is the new cloud-based platform to automate actions across a variety of applications and services. Thanks to hybrid technology, you can also integrate Power Automate into your SharePoint Server environments using the On-Premises Data Gateway. Each related user must be assigned a Power Apps Plan 1 license to use Power Automate with SharePoint Server, which is not included as part of the SharePoint Server license. In addition, Power Automate is currently optimized for non-interactive workflows with SharePoint Server. If you require interactive workflows, we recommend exploring the SharePoint 2013 Workflow platform instead. * The SharePoint 2010 Workflow platform is also supported in SharePoint Server 2019 for backward compatibility. This allows SharePoint Sever 2019 to run legacy workflows from previous versions of SharePoint Server. Although SharePoint 2010 workflows are still supported, we don't recommend building new workflows using this technology. Instead, we recommend exploring either SharePoint 2013 workflows or Power Automate.
SharePoint Differences Search 2016 2019 https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/live/SharePoint/SharePointServer/search/differences-search-2016-2019.md
description: "Learn about the differences between the search experiences in Shar
[!INCLUDE[appliesto-2013-2016-2019-xxx-md](../includes/appliesto-2013-2016-2019-xxx-md.md)]
-In addition to the classic search experience, SharePoint Server 2019 comes with a modern search experience. Both search experiences use the same search index to find results.
+In addition to the classic search experience, SharePoint Server 2019 comes with a modern search experience. Both search experiences use the same search index to find results.
-As a user, the most visual difference is that in modern search, you see results even before you start typing in the search box, and the results update as you type. [Learn about the modern search experience](https://support.office.com/article/3f56ab51-f10f-4a34-a8c6-bfe02f44896d)ΓÇï.
+As a user, the most visual difference is that in modern search, you see results even before you start typing in the search box, and the results update as you type. [Learn about the modern search experience](https://support.office.com/article/3f56ab51-f10f-4a34-a8c6-bfe02f44896d).
As a search administrator, you can not disable classic or modern search. Users get the classic search experience on publishing sites, classic team sites, and in the Search Center. Users get the modern search experience on the SharePoint home page, communication sites, and modern team sites. There are some differences between the search experiences from a search administrator's perspective.
-Search administrators can customize the *classic* search experience, but only impact some aspects of the modern search experience. There aren't separate search settings for the modern search experience. Instead certain of the classic search settings **also** apply to the modern search experience:
+Search administrators can customize the *classic* search experience, but only impact some aspects of the modern search experience. There aren't separate search settings for the modern search experience. Instead certain of the classic search settings **also** apply to the modern search experience:
- The [search schema](manage-the-search-schema.md) determines how content is collected in and retrieved from the search index. Because both search experiences use the same search index to find search results, any changes you make to the search schema, apply to both experiences. The following search schema settings donΓÇÖt affect the modern search experience:
- - Sortable
- - Refinable
- - Company name extraction
- - Custom entity extraction
+ - Sortable
+ - Refinable
+ - Company name extraction
+ - Custom entity extraction
- The modern search experience only shows results from the default result source. If you change the default [result source](configure-result-sources-for-search.md), both search experiences are impacted. - If you temporarily [remove a search result](./delete-items-from-the-search-index-or-from-search-results.md#remove-an-item-from-the-search-results), the result is removed in both search experiences. - When you create a [promoted result](manage-query-rules.md) at the tenant level, users can see it in both search experiences. In the modern search experience, users only see promoted results when theyΓÇÖve filtered to All result types (default filter) on the search results page and only when they search across all sites.
-Unlike the classic search results page, the modern search results page isnΓÇÖt built with web parts. You canΓÇÖt customize the modern search results page or create additional search results pages.
+Unlike the classic search results page, the modern search results page isnΓÇÖt built with web parts. You canΓÇÖt customize the modern search results page or create additional search results pages.
SharePoint Manage A Paused Search Service Application https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/live/SharePoint/SharePointServer/search/manage-a-paused-search-service-application.md
We'll show you how you can find out if and why the Search service application is
3. At the Microsoft PowerShell command prompt, type the following command(s) to find out if the Search service application is paused.
- ```
- $ssa.IsPaused() -ne 0
- ```
+ ```powershell
+ $ssa.IsPaused() -ne 0
+ ```
-If this command returns **False**, the Search service application is running.
-
-If this command returns **True**, the Search service application is paused. Go to step 4 to find out why, and what action you should take.
+ If this command returns **False**, the Search service application is running.
+
+ If this command returns **True**, the Search service application is paused. Go to step 4 to find out why, and what action you should take.
4. At the Microsoft PowerShell command prompt, type the following command(s) until you find the reason why the Search service application is paused.
-| **Command** | **If the command returns True, the Search service application is paused for this reason:** | **Action** |
-| : | :-- | :- |
-| `($ssa.IsPaused() -band 0x01) -ne 0` | A change in the number of crawl components or crawl databases is in progress. | Wait until the topology change completes. |
-| `($ssa.IsPaused() -band 0x02) -ne 0` | A backup or restore procedure is in progress. | Wait until the backup or restore completes. After the procedure completes, run the command `$ssa.ForceResume(0x02)` to verify. For more information, see [Restore Search service applications in SharePoint Server](../administration/restore-a-search-service-application.md). |
-| `($ssa.IsPaused() -band 0x04) -ne 0` | A backup of the Volume Shadow Copy Service (VSS) is in progress. | Wait until the backup completes. After the VSS backup completes, run the command `$ssa.ForceResume(0x02)` to verify. |
-| `($ssa.IsPaused() -band 0x08) -ne 0` | One or more servers in the search topology that host query components are offline. | Wait until the servers are available again. |
-| `($ssa.IsPaused() -band 0x20) -ne 0` | One or more crawl databases in the search topology are being rebalanced. | Wait until the operation completes. |
-| `($ssa.IsPaused() -band 0x40) -ne 0` | One or more link databases in the search topology are being rebalanced. | Wait until the operation completes. |
-| `($ssa.IsPaused() -band 0x80) -ne 0` | An administrator has manually paused the Search service application. | If you know the reason, you can resume the Search service application. Run the command `$ssa.resume()` to resume the Search service application. <br/><br/>If you don't know the reason, find out why someone has manually paused the Search service application. |
-| `($ssa.IsPaused() -band 0x100) -ne 0` | The search index is being deleted. | Wait until the search index is deleted. |
-| `($ssa.IsPaused() -band 0x200) -ne 0` | The search index is being repartitioned. | Wait until the operation completes. For more information, see [Manage the index component in SharePoint Server](manage-the-index-component.md). |
-
-After you've waited until the operation completes, at the Microsoft PowerShell command prompt, type the following command to make sure that the Search service application is running:
-
-```
-$ssa.IsPaused() -ne 0
-```
-
-If this command returns **False**, the Search service application is running.
-
-If this command returns **True**, the Search service application is paused. Re-run the commands from step 4 to find out why.
+ | Command | If the command returns True, the Search service application is paused for this reason: | Action |
+ |:|:|:|
+ | `($ssa.IsPaused() -band 0x01) -ne 0` | A change in the number of crawl components or crawl databases is in progress. | Wait until the topology change completes. |
+ | `($ssa.IsPaused() -band 0x02) -ne 0` | A backup or restore procedure is in progress. | Wait until the backup or restore completes. After the procedure completes, run the command `$ssa.ForceResume(0x02)` to verify. For more information, see [Restore Search service applications in SharePoint Server](../administration/restore-a-search-service-application.md). |
+ | `($ssa.IsPaused() -band 0x04) -ne 0` | A backup of the Volume Shadow Copy Service (VSS) is in progress. | Wait until the backup completes. After the VSS backup completes, run the command `$ssa.ForceResume(0x02)` to verify. |
+ | `($ssa.IsPaused() -band 0x08) -ne 0` | One or more servers in the search topology that host query components are offline. | Wait until the servers are available again. |
+ | `($ssa.IsPaused() -band 0x20) -ne 0` | One or more crawl databases in the search topology are being rebalanced. | Wait until the operation completes. |
+ | `($ssa.IsPaused() -band 0x40) -ne 0` | One or more link databases in the search topology are being rebalanced. | Wait until the operation completes. |
+ | `($ssa.IsPaused() -band 0x80) -ne 0` | An administrator has manually paused the Search service application. | If you know the reason, you can resume the Search service application. Run the command `$ssa.resume()` to resume the Search service application. <br/><br/>If you don't know the reason, find out why someone has manually paused the Search service application. |
+ | `($ssa.IsPaused() -band 0x100) -ne 0` | The search index is being deleted. | Wait until the search index is deleted. |
+ | `($ssa.IsPaused() -band 0x200) -ne 0` | The search index is being repartitioned. | Wait until the operation completes. For more information, see [Manage the index component in SharePoint Server](manage-the-index-component.md). |
+
+ After you've waited until the operation completes, at the Microsoft PowerShell command prompt, type the following command to make sure that the Search service application is running:
+
+ ```powershell
+ $ssa.IsPaused() -ne 0
+ ```
+
+ If this command returns **False**, the Search service application is running.
+
+ If this command returns **True**, the Search service application is paused. Re-run the commands from step 4 to find out why.
**Resume a paused Search service application in SharePoint Server** To resume a paused Search service application, use the following PowerShell.
-```
+```powershell
$ssa = Get-SPEnterpriseSearchServiceApplication -Identity MySSA $ssa | Resume-SPEnterpriseSearchServiceApplication
+```