Merge pull request #248719 from v-thepet/remaining

Court72 · web-flow · commit 37b0cb22ce95 · 2023-08-18T11:55:56.000-07:00
Policheck updates – August 17 | Bulk Updates
diff --git a/articles/active-directory/authentication/howto-mfa-mfasettings.md b/articles/active-directory/authentication/howto-mfa-mfasettings.md
@@ -200,7 +200,7 @@ The following table lists more numbers for different countries.
 | Sri Lanka            | +94 117750440   |
 | Sweden               | +46 701924176   |
 | Taiwan               | +886 277515260  |
-| Turkey               | +90 8505404893  |
+| Türkiye              | +90 8505404893  |
 | Ukraine              | +380 443332393  |
 | United Arab Emirates | +971 44015046   |
 | Vietnam              | +84 2039990161  |
diff --git a/articles/active-directory/external-identities/customers/how-to-customize-languages-customers.md b/articles/active-directory/external-identities/customers/how-to-customize-languages-customers.md
@@ -77,7 +77,7 @@ The following languages are supported in the customer tenant:
    - Spanish (Spain)
    - Swedish (Sweden)
    - Thai (Thailand)
-   - Turkish (Turkey)
+   - Turkish (Türkiye)
    - Ukrainian (Ukraine)
    
 6. Customize the elements on the **Basics**, **Layout**, **Header**, **Footer**, **Sign-in form**, and **Text** tabs. For detailed instructions, see [Customize the branding and end-user experience](how-to-customize-branding-customers.md).
diff --git a/articles/app-service/reference-app-settings.md b/articles/app-service/reference-app-settings.md
@@ -599,7 +599,7 @@ The following environment variables are related to the [push notifications](/pre
 | `WEBSITE_PUSH_TAGS_DYNAMIC` | Read-only. Contains a list of tags in the notification registration that were added automatically. | 
 
 >[!NOTE]
-> This article contains references to the term *whitelist*, a term that Microsoft no longer uses. When the term is removed from the software, we’ll remove it from this article.
+> This article contains references to a term that Microsoft no longer uses. When the term is removed from the software, we’ll remove it from this article.
 
 <!-- 
 ## WellKnownAppSettings
diff --git a/articles/azure-netapp-files/faq-application-resilience.md b/articles/azure-netapp-files/faq-application-resilience.md
@@ -45,12 +45,9 @@ The scale-out architecture would be comprised of multiple IBM MQ multi-instance
 
 ## I'm running Apache ActiveMQ with LevelDB or KahaDB on Azure NetApp Files. What precautions can I take to avoid disruptions due to storage service maintenance events despite using the *NFS* protocol?
 
->[!NOTE]
-> This section contains references to the terms *slave* and *master*, terms that Microsoft no longer uses. When the term is removed from the software, we'll remove it from this article.
-
 If you're running the Apache ActiveMQ, it's recommended to deploy [ActiveMQ High Availability with Pluggable Storage Lockers](https://www.openlogic.com/blog/pluggable-storage-lockers-activemq). 
 
-ActiveMQ high availability (HA) models ensure that a broker instance is always online and able to process message traffic. The two most common ActiveMQ HA models involve sharing a filesystem over a network. The purpose is to provide either LevelDB or KahaDB to the active and passive broker instances. These HA models require that an OS-level lock be obtained and maintained on a file in the LevelDB or KahaDB directories, called "lock." There are some problems with this ActiveMQ HA model. They can lead to  a "no-master" situation, where the "slave" isn’t aware that it can lock the file.  They can also lead to a "master-master" configuration that results in index or journal corruption and ultimately message loss. Most of these problems stem from factors outside of ActiveMQ's control. For instance, a poorly optimized NFS client can cause locking data to become stale under load, leading to “no-master” downtime during failover. 
+ActiveMQ high availability (HA) models ensure that a broker instance is always online and able to process message traffic. The two most common ActiveMQ HA models involve sharing a filesystem over a network. The purpose is to provide either LevelDB or KahaDB to the active and passive broker instances. These HA models require that an OS-level lock be obtained and maintained on a file in the LevelDB or KahaDB directories, called "lock." There are some problems with this ActiveMQ HA model. They can lead to  a "no-master" situation, where the replica isn’t aware that it can lock the file.  They can also lead to a "master-master" configuration that results in index or journal corruption and ultimately message loss. Most of these problems stem from factors outside of ActiveMQ's control. For instance, a poorly optimized NFS client can cause locking data to become stale under load, leading to “no-master” downtime during failover. 
 
 Because most problems with this HA solution stem from inaccurate OS-level file locking, the ActiveMQ community [introduced the concept of a pluggable storage locker](https://www.openlogic.com/blog/pluggable-storage-lockers-activemq) in version 5.7 of the broker. This approach allows a user to take advantage of a different means of the shared lock, using a row-level JDBC database lock as opposed to an OS-level filesystem lock. For support or consultancy on ActiveMQ HA architectures and deployments, you should [contact OpenLogic by Perforce](https://www.openlogic.com/contact-us).
 
diff --git a/articles/communication-services/how-tos/ui-library-sdk/includes/localization/ios.md b/articles/communication-services/how-tos/ui-library-sdk/includes/localization/ios.md
@@ -47,7 +47,7 @@ The following table of `locale` with out of the box translations. If you want to
 | Spanish | es | es |
 | Spanish (Spain) | esES | es-ES |
 | Turkish | tr | tr |
-| Turkish (Turkey) | trTR | tr-TR |
+| Turkish (Türkiye) | trTR | tr-TR |
 
 You can also obtain list of `locale` by the static function `SupportedLocale.values` will return list of Locale structs.
 
diff --git a/articles/cost-management-billing/microsoft-customer-agreement/microsoft-customer-agreement-faq.yml b/articles/cost-management-billing/microsoft-customer-agreement/microsoft-customer-agreement-faq.yml
@@ -52,7 +52,7 @@ sections:
              | Singapore | Slovakia | Slovenia | South Africa |
              | Spain | Sri Lanka | Sweden | Switzerland |
              | Taiwan | Tajikistan | Tanzania | Thailand |
-             | Trinidad and Tobago | Tunisia | Turkey | Turkmenistan |
+             | Trinidad and Tobago | Tunisia | Türkiye | Turkmenistan |
              | Uganda | UK | Ukraine | United Arab Emirates |
              | United States | Uruguay | Uzbekistan | Venezuela |
              | Vietnam | Virgin Islands of the United States | Yemen | Zambia |
diff --git a/articles/event-hubs/event-hubs-kafka-connect-debezium.md b/articles/event-hubs/event-hubs-kafka-connect-debezium.md
@@ -12,7 +12,7 @@ ms.date: 10/18/2021
 This tutorial walks you through how to set up a change data capture based system on Azure using [Event Hubs](./event-hubs-about.md?WT.mc_id=devto-blog-abhishgu) (for Kafka), [Azure DB for PostgreSQL](../postgresql/overview.md) and Debezium. It will use the [Debezium PostgreSQL connector](https://debezium.io/documentation/reference/1.2/connectors/postgresql.html) to stream database modifications from PostgreSQL to Kafka topics in Event Hubs
 
 > [!NOTE]
-> This article contains references to the term *whitelist*, a term that Microsoft no longer uses. When the term is removed from the software, we'll remove it from this article.
+> This article contains references to a term that Microsoft no longer uses. When the term is removed from the software, we'll remove it from this article.
 
 In this tutorial, you take the following steps:
 
diff --git a/articles/event-hubs/event-hubs-kafka-mirror-maker-tutorial.md b/articles/event-hubs/event-hubs-kafka-mirror-maker-tutorial.md
@@ -16,7 +16,7 @@ This tutorial shows how to mirror a Kafka broker into an Azure Event Hubs using
 > This sample is available on [GitHub](https://github.com/Azure/azure-event-hubs-for-kafka/tree/master/tutorials/mirror-maker)
 
 > [!NOTE]
-> This article contains references to the term *whitelist*, a term that Microsoft no longer uses. When the term is removed from the software, we'll remove it from this article.
+> This article contains references to a term that Microsoft no longer uses. When the term is removed from the software, we'll remove it from this article.
 
 In this tutorial, you learn how to:
 > [!div class="checklist"]
diff --git a/articles/hdinsight/interactive-query/apache-hive-warehouse-connector-zeppelin.md b/articles/hdinsight/interactive-query/apache-hive-warehouse-connector-zeppelin.md
@@ -13,7 +13,7 @@ ms.date: 07/18/2022
 HDInsight Spark clusters include Apache Zeppelin notebooks with different interpreters. In this article, we'll focus only on the Livy interpreter to access Hive tables from Spark using Hive Warehouse Connector.
 
 > [!NOTE]
-> This article contains references to the term *whitelist*, a term that Microsoft no longer uses. When the term is removed from the software, we'll remove it from this article.
+> This article contains references to a term that Microsoft no longer uses. When the term is removed from the software, we'll remove it from this article.
 
 ## Prerequisite
 
diff --git a/articles/hdinsight/kafka/apache-kafka-mirroring.md b/articles/hdinsight/kafka/apache-kafka-mirroring.md
@@ -254,7 +254,7 @@ Configure IP advertising to enable a client to connect by using broker IP addres
 ## Start MirrorMaker
 
 > [!NOTE]
-> This article contains references to the term *whitelist*, a term that Microsoft no longer uses. When the term is removed from the software, we'll remove it from this article.
+> This article contains references to a term that Microsoft no longer uses. When the term is removed from the software, we'll remove it from this article.
 
 1. From the SSH connection to the secondary cluster, use the following command to start the MirrorMaker process:
 
diff --git a/articles/managed-instance-apache-cassandra/monitor-clusters.md b/articles/managed-instance-apache-cassandra/monitor-clusters.md
@@ -135,7 +135,7 @@ Use the [Azure Monitor REST API](/rest/api/monitor/diagnosticsettings/createorup
 ## Audit whitelist
 
 > ![NOTE]
-> This article contains references to the term *whitelist*, a term that Microsoft no longer uses. When the term is removed from the software, we'll remove it from this article.
+> This article contains references to a term that Microsoft no longer uses. When the term is removed from the software, we'll remove it from this article.
 
 By default, audit logging creates a record for every login attempt and CQL query. The result can be rather overwhelming and increase overhead. You can use the audit whitelist feature in Cassandra 3.11 to set what operations *don't* create an audit record. The audit whitelist feature is enabled by default in Cassandra 3.11. To learn how to configure your whitelist, see [Role-based whitelist management](https://github.com/Ericsson/ecaudit/blob/release/c2.2/doc/role_whitelist_management.md). 
 
diff --git a/articles/web-application-firewall/afds/waf-front-door-geo-filtering.md b/articles/web-application-firewall/afds/waf-front-door-geo-filtering.md
@@ -251,7 +251,7 @@ You can configure a geo-filtering policy for your Azure Front Door instance by u
 | TM | Turkmenistan|
 | TN | Tunisia|
 | TO | Tonga|
-| TR | Turkey|
+| TR | Türkiye|
 | TT | Trinidad and Tobago|
 | TV | Tuvalu|
 | TW | Taiwan|
diff --git a/includes/mdfc/mdfc-recs-gcp-compute.md b/includes/mdfc/mdfc-recs-gcp-compute.md
@@ -14,7 +14,7 @@ There are **26** GCP recommendations in this category.
 |[Compute Engine VMs should use the Container-Optimized OS](https://portal.azure.com/#blade/Microsoft_Azure_Security/RecommendationsBlade/assessmentKey/3e33004b-f0b8-488d-85ed-61336c7ad4ca) |This recommendation evaluates the config property of a node pool for the key-value pair, 'imageType': 'COS'. |Low |
 |[Ensure 'Block Project-wide SSH keys' is enabled for VM instances](https://portal.azure.com/#blade/Microsoft_Azure_Security/RecommendationsBlade/assessmentKey/00f8a6a6-cf69-4c11-822e-3ebf4910e545) |It is recommended to use Instance specific SSH key(s) instead of using common/shared project-wide SSH key(s) to access Instances. <br />Project-wide SSH keys are stored in Compute/Project-meta-data. Project wide SSH keys can be used to login into all the instances within project. Using project-wide SSH keys eases the SSH key management but if compromised, poses the security risk which can impact all the instances within project. <br> It is recommended to use Instance specific SSH keys which can limit the attack surface if the SSH keys are compromised. |Medium |
 |[Ensure Compute instances are launched with Shielded VM enabled](https://portal.azure.com/#blade/Microsoft_Azure_Security/RecommendationsBlade/assessmentKey/1a4b3b3a-7de9-4aa4-a29b-580d59b43f79) |To defend against against advanced threats and ensure that the boot loader and firmware on your VMs are signed and untampered, it is recommended that Compute instances are launched with Shielded VM enabled.<br>Shielded VMs are virtual machines (VMs) on Google Cloud Platform hardened by a set of security controls that help defend against rootkits and bootkits.<br>Shielded VM offers verifiable integrity of your Compute Engine VM instances, so you can be confident your instances haven't been compromised by boot- or kernel-level malware or rootkits.<br>Shielded VM's verifiable integrity is achieved through the use of Secure Boot, virtual trusted platform module (vTPM)-enabled Measured Boot, and integrity monitoring.<br>Shielded VM instances run firmware which is signed and verified using Google's Certificate Authority, ensuring that the instance's firmware is unmodified and establishing the root of trust for Secure Boot.<br>Integrity monitoring helps you understand and make decisions about the state of your VM instances and the Shielded VM vTPM enables Measured Boot by performing the measurements needed to create a known good boot baseline, called the integrity policy baseline.<br>The integrity policy baseline is used for comparison with measurements from subsequent VM boots to determine if anything has changed.<br>Secure Boot helps ensure that the system only runs authentic software by verifying the digital signature of all boot components, and halting the boot process if signature verification fails. |High |
-|[Ensure 'Enable connecting to serial ports' is not enabled for VM Instance](https://portal.azure.com/#blade/Microsoft_Azure_Security/RecommendationsBlade/assessmentKey/7e060336-2c9e-4289-a2a6-8d301bad47bb) |Interacting with a serial port is often referred to as the serial console, which is similar to using a terminal window, in that input and output is entirely in text mode and there is no graphical interface or mouse support.<br>If you enable the interactive serial console on an instance, clients can attempt to connect to that instance from any IP address. Therefore interactive serial console support should be disabled.<br>A virtual machine instance has four virtual serial ports. Interacting with a serial port is similar to using a terminal window, in that input and output is entirely in text mode and there is no graphical interface or mouse support.<br>The instance's operating system, BIOS, and other system-level entities often write output to the serial ports, and can accept input such as commands or answers to prompts.<br>Typically, these system-level entities use the first serial port (port 1) and serial port 1 is often referred to as the serial console.<br>The interactive serial console does not support IP-based access restrictions such as IP whitelists. If you enable the interactive serial console on an instance, clients can attempt to connect to that instance from any IP address.<br>This allows anybody to connect to that instance if they know the correct SSH key, username, project ID, zone, and instance name.<br>Therefore interactive serial console support should be disabled. |Medium |
+|[Ensure 'Enable connecting to serial ports' is not enabled for VM Instance](https://portal.azure.com/#blade/Microsoft_Azure_Security/RecommendationsBlade/assessmentKey/7e060336-2c9e-4289-a2a6-8d301bad47bb) |Interacting with a serial port is often referred to as the serial console, which is similar to using a terminal window, in that input and output is entirely in text mode and there is no graphical interface or mouse support.<br>If you enable the interactive serial console on an instance, clients can attempt to connect to that instance from any IP address. Therefore interactive serial console support should be disabled.<br>A virtual machine instance has four virtual serial ports. Interacting with a serial port is similar to using a terminal window, in that input and output is entirely in text mode and there is no graphical interface or mouse support.<br>The instance's operating system, BIOS, and other system-level entities often write output to the serial ports, and can accept input such as commands or answers to prompts.<br>Typically, these system-level entities use the first serial port (port 1) and serial port 1 is often referred to as the serial console.<br>The interactive serial console does not support IP-based access restrictions such as IP allowlists. If you enable the interactive serial console on an instance, clients can attempt to connect to that instance from any IP address.<br>This allows anybody to connect to that instance if they know the correct SSH key, username, project ID, zone, and instance name.<br>Therefore interactive serial console support should be disabled. |Medium |
 |[Ensure 'log_duration' database flag for Cloud SQL PostgreSQL instance is set to 'on'](https://portal.azure.com/#blade/Microsoft_Azure_Security/RecommendationsBlade/assessmentKey/272820a7-06ce-44b3-8318-4ec1f82237dc) |Enabling the log_hostname setting causes the duration of each completed statement to be logged.<br> This does not logs the text of the query and thus behaves different from the log_min_duration_statement flag.<br> This parameter cannot be changed after session start.<br> Monitoring the time taken to execute the queries can be crucial in identifying any resource hogging queries and assessing the performance of the server.<br> Further steps such as load balancing and use of optimized queries can be taken to ensure the performance and stability of the server.<br> This recommendation is applicable to PostgreSQL database instances. |Low |
 |[Ensure 'log_executor_stats' database flag for Cloud SQL PostgreSQL instance is set to 'off'](https://portal.azure.com/#blade/Microsoft_Azure_Security/RecommendationsBlade/assessmentKey/19711549-76eb-4f1f-b43b-b1048e66c1f0) |The PostgreSQL executor is responsible to execute the plan handed over by the PostgreSQL planner.<br> The executor processes the plan recursively to extract the required set of rows.<br> The "log_executor_stats" flag controls the inclusion of PostgreSQL executor performance statistics in the PostgreSQL logs for each query.<br> The "log_executor_stats" flag enables a crude profiling method for logging PostgreSQL executor performance statistics which even though can be useful for troubleshooting, it may increase the amount of logs significantly and have performance overhead.<br> This recommendation is applicable to PostgreSQL database instances.<br>  |Low |
 |[Ensure 'log_min_error_statement' database flag for Cloud SQL PostgreSQL instance is set to 'Error' or stricter](https://portal.azure.com/#blade/Microsoft_Azure_Security/RecommendationsBlade/assessmentKey/50a1058e-925b-4998-9d93-5eaa8f7021a3) |The "log_min_error_statement" flag defines the minimum message severity level that are considered as an error statement.<br> Messages for error statements are logged with the SQL statement.<br> Valid values include "DEBUG5", "DEBUG4", "DEBUG3", "DEBUG2", "DEBUG1", "INFO", "NOTICE", "WARNING", "ERROR", "LOG", "FATAL", and "PANIC".<br> Each severity level includes the subsequent levels mentioned above.<br> Ensure a value of ERROR or stricter is set.<br> Auditing helps in troubleshooting operational problems and also permits forensic analysis.<br> If "log_min_error_statement" is not set to the correct value, messages may not be classified as error messages appropriately.<br> Considering general log messages as error messages would make is difficult to find actual errors and considering only stricter severity levels as error messages may skip actual errors to log their SQL statements.<br> The "log_min_error_statement" flag should be set to "ERROR" or stricter.<br> This recommendation is applicable to PostgreSQL database instances.  |Low |
