Revising URL to remove HTTPS formatting.

TIP FOR LINKS: Links to docs.microsoft.com content cannot publish with an HTTPS path. Instead, we can use a relative link (as done here) for a .md file in the same repository, or a path to the product/file/article, which would in this case have been (/intune/apps/intune-management-extension.md).   One other consideration (which isn't an issue here) is we never include the language path of the URL (like en-us). The absence of a language path ensures the reader will be linked to a content version that matches their browsers default language (if  that content version is available), and if it's not available, they are linked to the default of English.

Author: Brenduns

memdocs/intune/protect/compliance-use-custom-settings.md

@@ -89,7 +89,7 @@ During the workflow to create a compliance policy, on the *Compliance settings*
 5. Complete the compliance policy creation task and assign the policy to devices.
 
 > [!NOTE]  
-> When a Windows device receives a compliance policy with custom settings, it checks for the presence of [Intune Management Extensions](https://docs.microsoft.com/mem/intune/apps/intune-management-extension). If not found, the device runs an MSI that installs the extensions, enabling the client to download and run PowerShell scripts that are part of a compliance policy, and to upload compliance results. Actions managed by the services include:
+> When a Windows device receives a compliance policy with custom settings, it checks for the presence of [Intune Management Extensions](../apps/intune-management-extension.md). If not found, the device runs an MSI that installs the extensions, enabling the client to download and run PowerShell scripts that are part of a compliance policy, and to upload compliance results. Actions managed by the services include:
 >
 > - Checking for new or updated PowerShell scripts every eight hours.
 > - Running the discovery scripts every eight hours.