Merge pull request #17811 from MicrosoftDocs/main

[AutoPublish] main to live - 04/22 15:30 PDT | 04/23 04:00 IST

Author: Ruchika-mittal01

intune/intune-service/configuration/device-restrictions-ios.md

@@ -729,9 +729,6 @@ You can also:
 
 - **Import** a CSV file with details about the app, including the URL. Use the `<app url>, <app name>, <app publisher>` format. Or, **Export** to create a list of the restricted apps you added, in the same format.
 
-  > [!TIP]
-  > You can import a list of preinstalled Apple apps by downloading the [Apple App BundleIDs CSV](https://github.com/microsoft/Intune-Config-Frameworks/blob/master/iOS/Supervised/Apple-App-BundleIDs.csv) (opens a Microsoft GitHub site).
-
 ## Wireless
 
 ### Settings apply to: Device enrollment and Automated device enrollment (supervised)

intune/intune-service/includes/intune-notices.md

@@ -86,7 +86,7 @@ Update your IT admin documentation and notify your helpdesk or users as needed.
 
 ### Move to new Microsoft Graph Beta API properties for Windows Autopilot self-deploying mode and pre-provisioning
 
-In late February 2025, a select number of old Microsoft Graph Beta API [windowsAutopilotDeploymentProfile](/graph/api/resources/intune-shared-windowsautopilotdeploymentprofile) properties used for Windows Autopilot self-deploying mode and pre-provisioning are removed and stop working. The same data can be found using newer Graph API properties.
+In late May 2025 (previously March), a select number of old Microsoft Graph Beta API [windowsAutopilotDeploymentProfile](/graph/api/resources/intune-shared-windowsautopilotdeploymentprofile) properties used for Windows Autopilot self-deploying mode and pre-provisioning are removed and stop working. The same data can be found using newer Graph API properties.
 
 #### How does this change affect you or your users?
 

intune/intune-service/protect/certificate-connector-install.md

@@ -72,6 +72,8 @@ After a connector installs, you can run the installation program again to uninst
 > The installer will attempt to install the .NET Framework 4.7.2. If you experience issues during this process you can choose to pre-install the .NET Framework using the [Microsoft .NET Framework 4.7.2 offline installer for Windows](https://support.microsoft.com/topic/microsoft-net-framework-4-7-2-offline-installer-for-windows-05a72734-2127-a15d-50cf-daf56d5faec2)
 
 ## Configure the certificate connector
+> [!Note]
+> If the connector is installed on Windows Server 2019 or an earlier version, the Microsoft Edge browser must be manually installed before starting the Certificate Connector for Microsoft Intune wizard.
 
 To configure the certificate connector, you use the **Certificate Connector for Microsoft Intune** wizard. The configuration can start automatically when you choose *Configure Now* at the end of a certificate connector install, or manually by opening an elevated command prompt and running **C:\Program Files\Microsoft Intune\PFXCertificateConnector\ConnectorUI\PFXCertificateConnectorUI.exe**. An example follows. The command must be run as an administrator.
 

intune/intune-service/protect/certificate-connector-prerequisites.md

@@ -42,7 +42,7 @@ Requirements for the computer where you install the connector software:
 - Windows Server 2012 R2 or later.
 
   > [!NOTE]
-  > The Server installation must include the Desktop Experience and support use of a browser. For more information, see [Install Server with Desktop Experience](/windows-server/get-started/getting-started-with-server-with-desktop-experience) in the Windows Server 2016 documentation.
+  > The Windows Server must be configured with the Desktop Experience, and for versions 2019 or earlier, the Microsoft Edge browser must be installed manually prior to initiating the connector setup. For more information, see [Install Server with Desktop Experience](/windows-server/get-started/getting-started-with-server-with-desktop-experience) in the Windows Server 2016 documentation.
 
 - .NET 4.7.2