Skip to content

Commit 76fbb00

Browse files
committed
Merge branch 'main' of https://github.com/microsoftdocs/memdocs-pr into streamline-settings-list-for-baselines
2 parents 3297464 + f51d7aa commit 76fbb00

43 files changed

Lines changed: 420 additions & 545 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

.openpublishing.redirection.json

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,25 @@
11
{
22
"redirections": [
3+
{
4+
"source_path": "memdocs/intune/configuration/vpn-settings-windows-phone-8-1.md",
5+
"redirect_url": "https://support.microsoft.com/windows/windows-phone-8-1-end-of-support-faq-7f1ef0aa-0aaf-0747-3724-5c44456778a3",
6+
"redirect_document_id": false
7+
},
8+
{
9+
"source_path": "memdocs/intune/configuration/email-settings-windows-phone-8-1.md",
10+
"redirect_url": "https://support.microsoft.com/windows/windows-phone-8-1-end-of-support-faq-7f1ef0aa-0aaf-0747-3724-5c44456778a3",
11+
"redirect_document_id": false
12+
},
13+
{
14+
"source_path": "memdocs/intune/configuration/device-restrictions-windows-phone-8-1.md",
15+
"redirect_url": "https://support.microsoft.com/windows/windows-phone-8-1-end-of-support-faq-7f1ef0aa-0aaf-0747-3724-5c44456778a3",
16+
"redirect_document_id": false
17+
},
18+
{
19+
"source_path": "memdocs/intune/configuration/custom-settings-windows-phone-8-1.md",
20+
"redirect_url": "https://support.microsoft.com/windows/windows-phone-8-1-end-of-support-faq-7f1ef0aa-0aaf-0747-3724-5c44456778a3",
21+
"redirect_document_id": false
22+
},
323
{
424
"source_path": "memdocs/intune/apps/store-apps-windows-phone-8-1.md",
525
"redirect_url": "/mem/intune/apps/apps-add",

memdocs/configmgr/comanage/tutorial-co-manage-clients.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -149,7 +149,7 @@ Automatic enrollment also lets users enroll their Windows 10 or later devices to
149149
> [!NOTE]
150150
> Some tenants may not have these options to configure.<!-- SCCMDocs#1230 -->
151151
>
152-
> **Microsoft Intune** is how you configure the MDM app for Azure AD. **Microsoft Intune Enrollment** is a specific Azure AD app that's created when you apply multi-factor authentication policies for iOS and Android enrollment. For more information, see [Require multi-factor authentication for Intune device enrollments](/intune/enrollment/multi-factor-authentication).
152+
> **Microsoft Intune** is how you configure the MDM app for Azure AD. **Microsoft Intune Enrollment** is a specific Azure AD app that's created when you apply multi-factor authentication policies for iOS and Android enrollment. For more information, see [Require multi-factor authentication for Intune device enrollments](../../intune/enrollment/multi-factor-authentication.md).
153153
154154
5. For MDM user scope, select **All**, and then **Save**.
155155

@@ -159,6 +159,9 @@ With hybrid Azure AD set-up and Configuration Manager client configurations in p
159159

160160
When you enable co-management, you'll assign a collection as a *Pilot group*. This is a group that contains a small number of clients to test your co-management configurations. We recommend you create a suitable collection before you start the procedure. Then you can select that collection without exiting the procedure to do so. You may need multiple collections since you can assign a different *Pilot group* for each workload.
161161

162+
> [!NOTE]
163+
> Since devices are enrolled in the Microsoft Intune service based on its Azure AD device token, and not a user token, only the default [Intune enrollment restriction](../../intune/enrollment/enrollment-restrictions-set.md) will apply to the enrollment.
164+
162165
### Enable co-management for versions 2111 and later
163166

164167
[!INCLUDE [Enable Co-management starting in version 2111](includes/enable-co-management-2111.md)]

memdocs/configmgr/core/get-started/2019/includes/1909/3556022.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -92,7 +92,7 @@ The tool doesn't currently have any tasks to migrate the database from on-premis
9292

9393
- [Backup and restore the database](../../../../servers/manage/backup-and-recovery.md)
9494
- [Configure a SQL Server Always On availability group and allow the data to replicate](../../../../servers/deploy/configure/sql-server-alwayson-for-a-highly-available-site-database.md#changes-for-site-backup)
95-
- [Migrate a SQL Server database to an Azure SQL Server VM](/azure/virtual-machines/windows/sql/virtual-machines-windows-migrate-sql)
95+
- [Migrate a SQL Server database to an Azure SQL Server VM](/azure/azure-sql/virtual-machines/windows/migrate-to-vm-from-sql-server)
9696

9797
#### Site system roles
9898

memdocs/configmgr/core/support/azure-migration-tool.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -144,7 +144,7 @@ The tool doesn't currently have any tasks to migrate the database from on-premis
144144

145145
- [Backup and restore the database](../servers/manage/backup-and-recovery.md)
146146
- [Configure a SQL Server Always On availability group and allow the data to replicate](../servers/deploy/configure/sql-server-alwayson-for-a-highly-available-site-database.md#changes-for-site-backup)
147-
- [Migrate a SQL Server database to an Azure SQL Server VM](/azure/virtual-machines/windows/sql/virtual-machines-windows-migrate-sql)
147+
- [Migrate a SQL Server database to an Azure SQL Server VM](/azure/azure-sql/virtual-machines/windows/migrate-to-vm-from-sql-server)
148148

149149
## Site system roles
150150

memdocs/configmgr/core/understand/site-size-performance-faq.yml

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -94,9 +94,9 @@ sections:
9494
For more information and recommendations on how to maximize Premium Storage performance and run SQL Servers in Azure IaaS VMs, see:
9595
9696
- [Optimize application performance](/azure/storage/storage-premium-storage-performance#optimize-application-performance)
97-
98-
- [Disks guidance](/azure/virtual-machines/windows/sql/virtual-machines-windows-sql-performance#disks-guidance)
99-
97+
98+
- [Disks guidance](/azure/azure-sql/virtual-machines/windows/performance-guidelines-best-practices-checklist#storage)
99+
100100
**Example: Azure-based site server**
101101
102102
[Sizing guidelines](../plan-design/configs/site-size-performance-guidelines.md#general-sizing-guidelines) for a colocated site server and SQL Server with **50,000** clients are eight cores, 32 GB, and 1200 IOPS for site server inboxes, and 2800 IOPS for SQL Server files.
@@ -110,7 +110,7 @@ sections:
110110
| 1xP30 (1024 GB) | 64k ReFS | SQL Server (all files<sup>2</sup>) | 2800 | 3112 |
111111
112112
1. This value is from [Example disk configurations](../plan-design/configs/site-size-performance-guidelines.md#example-disk-configurations).
113-
2. [Azure guidance](/azure/virtual-machines/windows/sql/virtual-machines-windows-sql-performance#disks-guidance) allows for placing the TempDB on the local, SSD-based *D:* drive, given it won't exceed available space and allows for additional disk I/O distribution.
113+
2. [Azure guidance](/azure/azure-sql/virtual-machines/windows/performance-guidelines-best-practices-checklist#storage) allows for placing the TempDB on the local, SSD-based *D:* drive, given it won't exceed available space and allows for additional disk I/O distribution.
114114
115115
**Example: Azure-based site server (for instant performance increase)**
116116
@@ -128,7 +128,7 @@ sections:
128128
129129
1. Disks are striped using Storage Spaces.
130130
2. This value is from [Example disk configurations](../plan-design/configs/site-size-performance-guidelines.md#example-disk-configurations). VM size limits performance.
131-
3. [Azure guidance](/azure/virtual-machines/windows/sql/virtual-machines-windows-sql-performance#disks-guidance) allows for placing the TempDB on the local, SSD-based *D:* drive, given it won't exceed available space and allows for additional disk I/O distribution.
131+
3. [Azure guidance](/azure/azure-sql/virtual-machines/windows/performance-guidelines-best-practices-checklist#storage) allows for placing the TempDB on the local, SSD-based *D:* drive, given it won't exceed available space and allows for additional disk I/O distribution.
132132
133133
If you need more performance in future, you can upsize your VM to a DS14v2, which will double CPU and memory. The additional disk bandwidth allowed by that VM size will also instantly boost the available disk IOPS on your previously configured disks.
134134
@@ -142,7 +142,7 @@ sections:
142142
143143
1. Disks are striped using Storage Spaces.
144144
2. This value is from [Example disk configurations](../plan-design/configs/site-size-performance-guidelines.md#example-disk-configurations). VM size limits performance.
145-
3. [Azure guidance](/azure/virtual-machines/windows/sql/virtual-machines-windows-sql-performance#disks-guidance) allows for placing the TempDB on the local, SSD-based *D:* drive, given it won't exceed available space and allows for additional disk I/O distribution.
145+
3. [Azure guidance](/azure/azure-sql/virtual-machines/windows/performance-guidelines-best-practices-checklist#storage) allows for placing the TempDB on the local, SSD-based *D:* drive, given it won't exceed available space and allows for additional disk I/O distribution.
146146
147147
- name: Other common SQL Server-related performance questions
148148
questions:

memdocs/configmgr/develop/core/servers/configure/how-to-configure-network-discovery.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
11
---
22
title: "Configure Network Discovery"
33
titleSuffix: "Configuration Manager"
4+
description: "Learn how to configure the Network Discovery settings in Configuration Manager."
45
ms.date: "09/20/2016"
56
ms.prod: "configuration-manager"
67
ms.technology: configmgr-sdk

memdocs/configmgr/sum/deploy-use/manage-office-365-proplus-updates.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ description: Configuration Manager synchronizes Microsoft 365 Apps client update
55
author: mestew
66
ms.author: mstewart
77
manager: dougeby
8-
ms.date: 01/05/2022
8+
ms.date: 05/09/2022
99
ms.topic: conceptual
1010
ms.prod: configuration-manager
1111
ms.technology: configmgr-sum
@@ -195,14 +195,14 @@ For update packages released on and after June 9, 2020, the title will begin wit
195195
</br>
196196
</br>
197197

198-
|New Channel name|Previous Channel name|
199-
|--|--|
200-
|Semi-Annual Enterprise Channel|Semi-Annual Channel|
201-
|Semi-Annual Enterprise Channel (Preview)|Semi-Annual Channel (Targeted)|
202-
|Monthly Enterprise Channel|NA|
203-
|Current Channel|Monthly Channel|
204-
|Current Channel (Preview)|Monthly Channel (Targeted)|
205-
|Beta Channel </br> </br> Beta Channel needs to be updated from the Office CDN on the internet instead of having Configuration Manager manage the update process. For more information, see [Use Configuration Manager to install Office Insider builds](https://insider.office.com/business/deploy/windows/configuration-manager).|Insider|
198+
|New Channel name|Previous Channel name|CDNBaseUrl|
199+
|--|--|--|
200+
|Semi-Annual Enterprise Channel|Semi-Annual Channel|`http://officecdn.microsoft.com/pr/7ffbc6bf-bc32-4f92-8982-f9dd17fd3114`|
201+
|Semi-Annual Enterprise Channel (Preview)|Semi-Annual Channel (Targeted)|`http://officecdn.microsoft.com/pr/b8f9b850-328d-4355-9145-c59439a0c4cf`|
202+
|Monthly Enterprise Channel|NA|`http://officecdn.microsoft.com/pr/55336b82-a18d-4dd6-b5f6-9e5095c314a6`|
203+
|Current Channel|Monthly Channel|`http://officecdn.microsoft.com/pr/492350f6-3a01-4f97-b9c0-c7c6ddf67d60`|
204+
|Current Channel (Preview)|Monthly Channel (Targeted)|`http://officecdn.microsoft.com/pr/64256afe-f5d9-4f86-8936-8840a6a4f5be`|
205+
|Beta Channel </br> </br> Beta Channel needs to be updated from the Office CDN on the internet instead of having Configuration Manager manage the update process. For more information, see [Use Configuration Manager to install Office Insider builds](https://insider.office.com/business/deploy/windows/configuration-manager).|Insider|`http://officecdn.microsoft.com/pr/5440fd1f-7ecb-4221-8110-145efaa6372f`|
206206

207207
For more information about how to modify your ADRs, see [Automatically deploy software updates](automatically-deploy-software-updates.md). For more information about the name change, see [Name change for Office 365 ProPlus](/deployoffice/name-change).
208208

memdocs/intune/apps/app-protection-policy-settings-ios.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ There are three categories of policy settings: *Data relocation*, *Access requir
4747
| Setting | How to use | Default value |
4848
|------|----------|-------|
4949
| **Backup Org data to iTunes and iCloud backups** | Select **Block** to prevent this app from backing up work or school data to iTunes and iCloud. Select **Allow** to allow this app to back up of work or school data to iTunes and iCloud. | **Allow** |
50-
| **Send Org data to other apps** | Specify what apps can receive data from this app: <ul><li>**All apps**: Allow transfer to any app. The receiving app will have the ability to read and edit the data.</li><li>**None**: Do not allow data transfer to any app, including other policy-managed apps. If the user performs a managed open-in function and transfers a document, the data will be encrypted and unreadable.</li><li> **Policy managed apps**: Allow transfer only to other policy-managed apps. <p><p>**Note:** _Users may be able to transfer content via Open-in or Share extensions to unmanaged apps on unenrolled devices or enrolled devices that allow sharing to unmanaged apps. Transferred data is encrypted by Intune and unreadable by unmanaged apps._</li><li> **Policy managed apps with OS sharing**: Only allow data transfer to other policy managed apps, as well as file transfers to other MDM managed apps on enrolled devices. <p><p>**Note:** _The **Policy managed apps with OS sharing** value is applicable to MDM enrolled devices only. If this setting is targeted to a user on an unenrolled device, the behavior of the **Policy managed apps** value applies. Users will be able to transfer unencrypted content via Open-in or Share extensions to any application allowed by the iOS MDM allowOpenFromManagedtoUnmanaged setting, assuming the sending app has the IntuneMAMUPN configured; for more information, see [How to manage data transfer between iOS apps in Microsoft Intune](data-transfer-between-apps-manage-ios.md). See https://developer.apple.com/business/documentation/Configuration-Profile-Reference.pdf for more information on this iOS/iPadOS MDM setting._<p><p></li><li>**Policy managed apps with Open-In/Share filtering**: Allow transfer only to other policy managed apps, and filter OS Open-in/Share dialogs to only display policy managed apps. To configure the filtering of the **Open-In/Share** dialog, it requires both the app(s) acting as the file/document source and the app(s) that can open this file/document to have the Intune SDK for iOS version 8.1.1 or above. <p><p>**Note:** _Users may be able to transfer content via Open-in or Share extensions to unmanaged apps if Intune private data type are supported by the app. Transferred data is encrypted by Intune and unreadable by unmanaged apps._</li></ul><br>In addition, when set to **Policy managed apps** or **None**, the Spotlight search (enables searching data within apps) and Siri shortcuts iOS features are blocked. <p><p>This policy can also apply to iOS/iPadOS Universal Links. General web links are managed by the **Open app links in Intune Managed Browser** policy setting. <p> There are some exempt apps and services to which Intune may allow data transfer by default. In addition, you can create your own exemptions if you need to allow data to transfer to an app that doesn't support Intune APP. See [data transfer exemptions](#data-transfer-exemptions) for more information. | **All apps** |
50+
| **Send Org data to other apps** | Specify what apps can receive data from this app: <ul><li>**All apps**: Allow transfer to any app. The receiving app will have the ability to read and edit the data.</li><li>**None**: Do not allow data transfer to any app, including other policy-managed apps. If the user performs a managed open-in function and transfers a document, the data will be encrypted and unreadable.</li><li> **Policy managed apps**: Allow transfer only to other policy-managed apps. <p><p>**Note:** _Users may be able to transfer content via Open-in or Share extensions to unmanaged apps on unenrolled devices or enrolled devices that allow sharing to unmanaged apps. Transferred data is encrypted by Intune and unreadable by unmanaged apps._</li><li> **Policy managed apps with OS sharing**: Only allow data transfer to other policy managed apps, as well as file transfers to other MDM managed apps on enrolled devices. <p><p>**Note:** _The **Policy managed apps with OS sharing** value is applicable to MDM enrolled devices only. If this setting is targeted to a user on an unenrolled device, the behavior of the **Policy managed apps** value applies. Users will be able to transfer unencrypted content via Open-in or Share extensions to any application allowed by the iOS MDM allowOpenFromManagedtoUnmanaged setting, assuming the sending app has the IntuneMAMUPN and IntuneMAMOID configured; for more information, see [How to manage data transfer between iOS apps in Microsoft Intune](data-transfer-between-apps-manage-ios.md). See https://developer.apple.com/business/documentation/Configuration-Profile-Reference.pdf for more information on this iOS/iPadOS MDM setting._<p><p></li><li>**Policy managed apps with Open-In/Share filtering**: Allow transfer only to other policy managed apps, and filter OS Open-in/Share dialogs to only display policy managed apps. To configure the filtering of the **Open-In/Share** dialog, it requires both the app(s) acting as the file/document source and the app(s) that can open this file/document to have the Intune SDK for iOS version 8.1.1 or above. <p><p>**Note:** _Users may be able to transfer content via Open-in or Share extensions to unmanaged apps if Intune private data type are supported by the app. Transferred data is encrypted by Intune and unreadable by unmanaged apps._</li></ul><br>In addition, when set to **Policy managed apps** or **None**, the Spotlight search (enables searching data within apps) and Siri shortcuts iOS features are blocked. <p><p>This policy can also apply to iOS/iPadOS Universal Links. General web links are managed by the **Open app links in Intune Managed Browser** policy setting. <p> There are some exempt apps and services to which Intune may allow data transfer by default. In addition, you can create your own exemptions if you need to allow data to transfer to an app that doesn't support Intune APP. See [data transfer exemptions](#data-transfer-exemptions) for more information. | **All apps** |
5151
| <ul>**Select apps to exempt** | This option is available when you select *Policy managed apps* for the previous option. | |
5252
| <ul>**Select universal links to exempt** | Specify which iOS/iPadOS [Universal Links](#universal-links) should open in the specified *unmanaged* application instead of the protected browser specified by the **Restrict web content transfer with other apps** setting. You must contact the application developer to determine the correct universal link format for each application. | |
5353
| <ul>**Select managed universal links** | Specify which iOS/iPadOS [Universal Links](#universal-links) should open in the specified *managed* application instead of the protected browser specified by the **Restrict web content transfer with other apps** setting. You must contact the application developer to determine the correct universal link format for each application. | |

memdocs/intune/apps/apps-add-android-for-work.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ keywords:
88
author: Erikre
99
ms.author: erikre
1010
manager: dougeby
11-
ms.date: 03/29/2022
11+
ms.date: 05/05/2022
1212
ms.topic: how-to
1313
ms.service: microsoft-intune
1414
ms.subservice: apps
@@ -235,6 +235,7 @@ For dedicated, fully managed, and corporate-owned work profile devices, you can
235235

236236
- **Default**: The app's updates are subject to default conditions (described above).
237237
- **High Priority**: The app will update as soon as possible from when a new update is released, disregarding all of the default conditions. This may be disruptive for some users since the update can occur while the device is being used.
238+
- **Postpone**: When the app receives a new update, a 90-day waiting period is triggered. After 90 days, the app is updated to the newest version available, even if that version was not the update that triggered the waiting period. Note that the 90-day window is not configurable. To terminate the waiting period early, change the update mode to either **Default** or **High Priority**.
238239

239240
To edit the app update mode:
240241
1. Sign in to the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431).

0 commit comments

Comments
 (0)