Merge pull request #224865 from MicrosoftDocs/main

1/24 AM Publish

Author: huypub

.openpublishing.redirection.json

@@ -18384,6 +18384,11 @@
             "redirect_url": "/azure/sentinel/enable-monitoring",
             "redirect_document_id": false
         },
+        {
+            "source_path_from_root": "/articles/sentinel/web-normalization-schema.md",
+            "redirect_url": "/azure/sentinel/normalization-schema-web",
+            "redirect_document_id": true
+        },
         {
             "source_path_from_root": "/articles/sentinel/dns-normalization-schema.md",
             "redirect_url": "/azure/sentinel/normalization-schema-dns",

articles/active-directory/authentication/concept-authentication-methods-manage.md

@@ -24,7 +24,7 @@ Azure Active Directory (Azure AD) allows the use of a range of authentication me
 
 ## Authentication methods policy
 
-The Authentication methods policy is the recommended way to manage authentication methods, including modern methods like passwordless authentication. [Authentication Policy Administrators](../roles/permissions-reference.md#authentication-policy-administrator) can edit this policy to enable authentication methods for specific users and groups. 
+The Authentication methods policy is the recommended way to manage authentication methods, including modern methods like passwordless authentication. [Authentication Policy Administrators](../roles/permissions-reference.md#authentication-policy-administrator) can edit this policy to enable authentication methods for all users or specific groups. 
 
 Methods enabled in the Authentication methods policy can typically be used anywhere in Azure AD - for both authentication and password reset scenarios. The exception is that some methods are inherently limited to use in authentication, such as FIDO2 and Windows Hello for Business, and others are limited to use in password reset, such as security questions. For more control over which methods are usable in a given authentication scenario, consider using the **Authentication Strengths** feature.
 
@@ -106,8 +106,9 @@ Tenants are set to either Pre-migration or Migration in Progress by default, dep
 > 
 > In the future, both of these features will be integrated with the Authentication methods policy.
 
-## Known issues
-Some customers may see the control to enable Voice call grayed out due to a licensing requirement, despite having a premium license. This is a known issue that we are actively working to fix.
+## Known issues and limitations
+- Some customers may see the control to enable Voice call grayed out due to a licensing requirement, despite having a premium license. This is a known issue that we are actively working to fix.
+- As a part of the public preview we removed the ability to target individual users. Previously targeted users will remain in the policy but we recommend moving them to a targeted group.
 
 ## Next steps
 

articles/active-directory/cloud-sync/what-is-cloud-sync.md

@@ -64,7 +64,7 @@ The following table provides a comparison between Azure AD Connect and Azure AD
 | Allow removing attributes from flowing from AD to Azure AD |● |● |
 | Allow advanced customization for attribute flows |● | |
 | Support for password writeback |● |● |
-| Support for device writeback|● | |
+| Support for device writeback|● |Customers should use [Cloud kerberose trust](https://learn.microsoft.com/windows/security/identity-protection/hello-for-business/hello-hybrid-cloud-kerberos-trust?tabs=intune) for this moving forward|
 | Support for group writeback|● | |
 | Support for merging user attributes from multiple domains|● | |
 | Azure AD Domain Services support|● | |

articles/api-management/api-management-faq.yml

@@ -36,7 +36,7 @@ sections:
         answer: |
           You have several options to secure the connection between the API Management gateway and your backend services, including:
           
-          * Use subscription key authentication. For more information, see [Import and publish your first API](import-and-publish.md).
+          * Use subscription key authentication. On its own, a subscription key isn't a strong form of authentication, but is often used along with another method. For more information, see [Authentication and authorization in API Management](authentication-authorization-overview.md). 
           * Use TLS mutual authentication as described in [How to secure back-end services by using client certificate authentication in Azure API Management](api-management-howto-mutual-certificates.md).
           * Use IP filtering on your back-end service. In all tiers of API Management except the Consumption tier, the IP address of the gateway remains constant. For more information, see [IP addresses of Azure API Management](api-management-howto-ip-addresses.md).
           * Connect your API Management instance to an [Azure virtual network](virtual-network-concepts.md).

articles/api-management/api-management-howto-app-insights.md

@@ -44,12 +44,15 @@ To use Application Insights, [create an instance of the Application Insights ser
     * This setting regularly validates whether the API Management gateway endpoint is responding. 
     * Results appear in the **Availability** pane of the Application Insights instance.
 1. Select **Create**.
-1. Check that the new Application Insights logger with an instrumentation key now appears in the list.  
-    :::image type="content" source="media/api-management-howto-app-insights/apim-app-insights-logger-2.png" alt-text="Screenshot that shows where to view the newly created Application Insights logger with instrumentation key":::
+1. Check that the new Application Insights logger now appears in the list.  
+    :::image type="content" source="media/api-management-howto-app-insights/apim-app-insights-logger-2.png" alt-text="Screenshot that shows where to view the newly created Application Insights logger.":::
 
 > [!NOTE]
 > Behind the scenes, a [Logger](/rest/api/apimanagement/current-ga/logger/create-or-update) entity is created in your API Management instance, containing the instrumentation key of the Application Insights instance.
 
+> [!TIP]
+> If you need to update the instrumentation key configured in the Application Insights logger, select the logger's row in the list (not the name of the logger). Enter the instrumentation key, and select **Save**.
+
 ## Enable Application Insights logging for your API
 
 1. Navigate to your **Azure API Management service instance** in the **Azure portal**.

articles/app-service/media/app-service-migrate-wordpress/post_startup_script_1.png

@@ -0,0 +1,147 @@
+---
+title: Migrate WordPress to App Service on Linux
+description: Migrate WordPress to App Service on Linux.
+author: msangapu-msft
+
+ms.topic: article
+ms.date: 01/20/2023
+ms.author: msangapu
+ms.devlang: php
+ms.custom: seodec18
+
+---
+# Migrate WordPress on App Service on Linux
+
+This article describes two ways to migrate WordPress from App Service on Windows or external hosting providers to App Service on Linux. 
+
+> [!NOTE]
+> Migrate the content to a test instance, validate all scenarios, and if everything works as expected, swap this instance to the production slot.
+>
+
+ You can migrate your site to WordPress on Azure App Service in two ways:
+
+ 1. WordPress plugin: All-In-One WP Migration
+ 2. Manual process of migration
+
+## Migrate WordPress with All-In-One WP Migration plugin
+
+This plugin is popular for migrating sites with ease. This approach is recommended for sites less than 256MB. If it's more, you can either **purchase the premium version** of the plugin or **migrate manually** using the steps outlined in [manual migration process](#manual-migration-process).
+
+By default, the file upload size for WordPress on Linux App Services is limited to 50MB, and it can be increased up to 256MB (Maximum Limit). To change the file upload  limit, add the following [Application Settings](configure-common.md?tabs=portal) in the App Service and save it.
+
+|    Application Setting Name    | Default Value | New Value   |
+|--------------------------------|---------------|-------------|
+|    UPLOAD_MAX_FILESIZE         |      50M      |   256M      |
+|    POST_MAX_SIZE               |      128M     |   256M      |
+
+> [!IMPORTANT]
+> Install All-In-One Migration plugin on both source and target sites.
+>
+
+### Export the data at source site
+
+1. Launch WordPress Admin page.
+1. Open All-In-One WP Migration plugin.
+1. Click on 'Export' option and specify the export type as file.
+1. Download the bundle.
+
+### Import the data at destination site
+
+1. Launch WordPress Admin page
+1. Open All-In-One WP Migration plugin
+1. Click on import option on the destination site, and upload the file downloaded in previous section
+1. Empty the caches in W3TC plugin (or any other caches) and validate the content of the site.
+    - Click on the **Performance** option given in the left sidebar of the admin panel to open the W3TC plugin.
+    - Then click on the **Dashboard** option shown below it.
+    - On the dashboard, you will see a button with the label **Empty All Caches**.
+
+## Manual migration process
+
+The prerequisite is that the WordPress on Linux Azure App Service must have been created with an appropriate hosting plan from here: [WordPress on Linux App Service](https://aka.ms/linux-wordpress).
+
+### Manually export the data at source site
+
+> [!NOTE]
+> Depending on the size of your content and your internet connection, this operation could take several minutes.
+>
+
+1. Download the **wp-content** folder from the source site. You can use popular FTP tools like [FileZilla](https://filezilla-project.org/download.php?type=client) to connect to the web server and download the content.
+
+1. Export the contents of the source database into an SQL file. You can perform this task either using MySQL client tools like HeidiSQL, [MySQL workbench](https://dev.mysql.com/downloads/workbench/), [PhpMyAdmin](https://docs.phpmyadmin.net/en/latest/setup.html) or through command line interface. For more information on exporting the database, refer to the following [documentation](https://dev.mysql.com/doc/workbench/en/wb-admin-export-import-management.html).
+
+### Manually import the data at destination site
+
+1. Create a new Wordpress app using our [WordPress on Linux App Service template](https://aka.ms/linux-wordpress)
+
+2. Open an SSH session using **WebSSH** from the Azure portal.
+![Web SSH](./media/app-service-migrate-wordpress/post_startup_script_1.png)
+
+3. Delete the existing content of **/home/site/wwwroot/wp-content** folder using the following command.
+
+   ```bash
+   rm -rf /home/site/wwwroot/wp-content/* 
+   ```
+
+4. Upload the new contents of **wp-content** folder using the File Manager. Click on the label that says '**Drag a File/Folder here to upload, or click to select one**'.
+
+5. You can either [use an existing MySQL database](https://github.com/Azure/wordpress-linux-appservice/blob/main/WordPress/using_an_existing_mysql_database.md) or migrate the content to a new Azure MySQL Flexible Server created by App Service on Linux. 
+
+
+> [!NOTE]
+> Azure Database for MySQL - Single Server is on the road to retirement by 16 September 2024. If your existing MySQL database is hosted on Azure Database for MySQL - Single Server, consider migrating to Azure Database for MySQL - Flexible Server using the following steps, or using [Azure Database Migration Service (DMS)](/mysql/single-server/whats-happening-to-mysql-single-server#migrate-from-single-server-to-flexible-server).
+>
+
+6. If you migrate the database, import the SQL file downloaded from the source database into the database of your newly created WordPress site. You can do it via the PhpMyAdmin dashboard available at **\<sitename\>.azurewebsites.net/phpmyadmin**. If you're unable to one single large SQL file, separate the files into parts and try uploading again. Steps to import the database through phpmyadmin are described [here](https://docs.phpmyadmin.net/en/latest/import_export.html#import).
+
+7. Launch the Azure Portal and navigate to your **App Service -> Configuration** blade. Update the database name in the **Application Settings** of App Service and save it. This will restart your App and the new changes will get reflected.  [Learn more: WordPress Application Settings](https://github.com/Azure/wordpress-linux-appservice/blob/main/WordPress/wordpress_application_settings.md)
+
+    |    Application Setting Name    | Update Required?                         |
+    |--------------------------------|------------------------------------------|
+    |    DATABASE_NAME               |      Yes, replace with the source (exported) database name |
+    |    DATABASE_HOST               |      Not Required                        |
+    |    DATABASE_USERNAME           |      Not Required                        |
+    |    DATABASE_PASSWORD           |      Not Required                        |
+
+    ![Database Application Settings](./media/app-service-migrate-wordpress/wordpress_database_application_settings.png)
+
+## Post migration actions
+
+### Install recommended plugins
+
+It's an optional step, after the site migration it is recommended to validate that you have the default recommended/equivalent plugins activated and configured accurate as before. If you're prohibited from not configuring them as per your organization governing policies, then you can uninstall the plugins.
+
+- The W3TC plugin should be activated and configured properly to use the local Redis cache server and Azure CDN/Blob Storage (if it was configured to use them originally). For more information on how to configure these, refer to the following documentations:
+
+  - [Local Redis Cache](https://github.com/Azure/wordpress-linux-appservice/blob/main/WordPress/wordpress_local_redis_cache.md)
+  - [Azure CDN](https://github.com/Azure/wordpress-linux-appservice/blob/main/WordPress/wordpress_azure_cdn.md)
+  - [Azure Blob Storage](https://github.com/Azure/wordpress-linux-appservice/blob/main/WordPress/wordpress_azure_blob_storage.md)
+
+- WP Smush plugin is activated and configured properly for image optimization. See [Image Compression](https://github.com/Azure/wordpress-linux-appservice/blob/main/WordPress/wordpress_image_compression.md) for more information on configuration.
+
+### Recommended WordPress settings
+
+The following WordPress settings are recommended. However, when the users migrate their custom sites, is it up to them to decide whether to use these settings or not.
+
+1. Open the WordPress Admin dashboard.
+2. Set the permalink structure to 'day and name', as it performs better compared to the plain permalinks that use the format **?p=123**.
+3. Under the comment settings, enable the option to break comments into pages.
+4. Show excerpts instead of the full post in the feed.
+
+## Search and replace (paths and domains)
+
+One common issue that users face during migration is that some of the contents of their old site use absolute urls/paths instead of relative ones. To resolve this issue, you can use plugins like [Search and Replace](https://wordpress.org/plugins/search-replace/) to update the database records.
+
+## Configuring custom domain
+
+To configure your site with a custom domain follow the steps described here: Tutorial: [Map existing custom DNS name](app-service-web-tutorial-custom-domain.md?tabs=a%2Cazurecli)
+
+## Migrating custom domain
+
+When you migrate a live site and its DNS domain name to App Service, that DNS name is already serving live traffic. You can avoid DNS resolution downtime by binding the active DNS name to your app as described in [Migrate an active DNS name](manage-custom-dns-migrate-domain.md).
+
+## Updating SSL certificates
+
+If your site is configured with SSL certs, then follow [Add and manage TLS/SSL certificates](configure-ssl-certificate.md?tabs=apex%2Cportal) to configure SSL.
+
+Next steps:
+[At-scale assessment of .NET web apps](/training/modules/migrate-app-service-migration-assistant/)

articles/app-service/media/app-service-migrate-wordpress/wordpress_database_application_settings.png

@@ -498,6 +498,8 @@
           href: /azure/developer/java/migration/migrate-weblogic-to-jboss-eap-on-azure-app-service?toc=/azure/app-service/toc.json&bc=/azure/bread/toc.json
         - name: Migrate WebSphere
           href: /azure/developer/java/migration/migrate-websphere-to-jboss-eap-on-azure-app-service?toc=/azure/app-service/toc.json&bc=/azure/bread/toc.json
+        - name: Migrate WordPress
+          href: migrate-wordpress.md
     - name: Cookbooks
       items:
         - name: Reference Architectures

articles/app-service/migrate-wordpress.md

@@ -1,5 +1,5 @@
 ---
-title: Use For containers in disconnected environments
+title: Use Form Recognizer containers in disconnected environments
 titleSuffix: Azure Applied AI Services
 description: Learn how to run Azure Cognitive Services Docker containers disconnected from the internet.
 ms.service: applied-ai-services