Merge branch 'MicrosoftDocs:main' into docs-editor/vminsights-performance-1694630539

Author: RepinStyle

articles/active-directory/authentication/how-to-mfa-registration-campaign.md

@@ -62,7 +62,7 @@ In addition to choosing who can be nudged, you can define how many days a user c
 
       ![Confirmation of approval](./media/how-to-nudge-authenticator-app/approved.png)
 
-   1. Authenticator app is now successfully set up as the user’s default sign-in method.
+   1. Authenticator app is now successfully set up as the user's default sign-in method.
 
       ![Installation complete](./media/how-to-nudge-authenticator-app/finish.png)
 
@@ -88,7 +88,7 @@ In addition to using the Azure portal, you can also enable the registration camp
 
 To configure the policy using Graph Explorer:
 
-1. Sign in to Graph Explorer and ensure you’ve consented to the **Policy.Read.All** and **Policy.ReadWrite.AuthenticationMethod** permissions.
+1. Sign in to Graph Explorer and ensure you've consented to the **Policy.Read.All** and **Policy.ReadWrite.AuthenticationMethod** permissions.
 
    To open the Permissions panel:
 

articles/active-directory/authentication/howto-mfa-mfasettings.md

@@ -206,7 +206,7 @@ The following table lists more numbers for different countries.
 | Vietnam              | +84 2039990161  |
 
 > [!NOTE]
-> When Azure AD Multi-Factor Authentication calls are placed through the public telephone network, sometimes the calls are routed through a carrier that doesn't support caller ID. Because of this, caller ID isn't guaranteed, even though Azure AD Multi-Factor Authentication always sends it. This applies both to phone calls and text messages provided by Azure AD Multi-Factor Authentication. If you need to validate that a text message is from Azure AD Multi-Factor Authentication, see [What SMS short codes are used for sending messages?](multi-factor-authentication-faq.yml#what-sms-short-codes-are-used-for-sending-sms-messages-to-my-users-).
+> When Azure AD Multi-Factor Authentication calls are placed through the public telephone network, sometimes the calls are routed through a carrier that doesn't support caller ID. Because of this, caller ID isn't guaranteed, even though Azure AD Multi-Factor Authentication always sends it. This applies both to phone calls and text messages provided by Azure AD Multi-Factor Authentication. If you need to validate that a text message is from Azure AD Multi-Factor Authentication, see [What short codes are used for sending messages?](multi-factor-authentication-faq.yml#what-short-codes-are-used-for-sending-text-messages-to-my-users-).
 
 To configure your own caller ID number, complete the following steps:
 
@@ -215,7 +215,7 @@ To configure your own caller ID number, complete the following steps:
 1. Select **Save**.
 
 > [!NOTE]
-> When Azure AD Multi-Factor Authentication calls are placed through the public telephone network, sometimes the calls are routed through a carrier that doesn't support caller ID. Because of this, caller ID isn't guaranteed, even though Azure AD Multi-Factor Authentication always sends it. This applies both to phone calls and text messages provided by Azure AD Multi-Factor Authentication. If you need to validate that a text message is from Azure AD Multi-Factor Authentication, see [What SMS short codes are used for sending messages?](multi-factor-authentication-faq.yml#what-sms-short-codes-are-used-for-sending-sms-messages-to-my-users-).
+> When Azure AD Multi-Factor Authentication calls are placed through the public telephone network, sometimes the calls are routed through a carrier that doesn't support caller ID. Because of this, caller ID isn't guaranteed, even though Azure AD Multi-Factor Authentication always sends it. This applies both to phone calls and text messages provided by Azure AD Multi-Factor Authentication. If you need to validate that a text message is from Azure AD Multi-Factor Authentication, see [What short codes are used for sending messages?](multi-factor-authentication-faq.yml#what-short-codes-are-used-for-sending-text-messages-to-my-users-).
 
 ### Custom voice messages
 

articles/active-directory/authentication/multi-factor-authentication-faq.yml

@@ -34,7 +34,7 @@ sections:
           * **Unique ID** (either user name or on-premises Multi-Factor Authentication Server ID)
           * **First and Last Name** (optional)
           * **Email Address** (optional)
-          * **Phone Number** (when using a voice call or SMS authentication)
+          * **Phone Number** (when using a voice call or text message authentication)
           * **Device Token** (when using mobile app authentication)
           * **Authentication Mode**
           * **Authentication Result**
@@ -49,27 +49,24 @@ sections:
           For more information, see [Data residency and customer data for Azure AD Multi-Factor Authentication](concept-mfa-data-residency.md).
           
       - question: |
-          What SMS short codes are used for sending SMS messages to my users?
+          What short codes are used for sending text messages to my users?
         answer: |
-          In the United States, we use the following SMS short codes:
+          In the United States, we use the following short codes:
           
           * *97671*
           * *69829*
           * *51789*
           * *99399*
           
-          In Canada, we use the following SMS short codes:
+          In Canada, we use the following short codes:
           
           * *759731*
           * *673801*
           
-          There's no guarantee of consistent SMS or voice-based Multi-Factor Authentication prompt delivery by the same number. In the interest of our users, we may add or remove short codes at any time as we make route adjustments to improve SMS deliverability.
+          There's no guarantee of consistent text message or voice-based multifactor authentication prompt delivery by the same number. In the interest of our users, we may add or remove short codes at any time as we make route adjustments to improve text message deliverability.
           
           We don't support short codes for countries or regions besides the United States and Canada.
           
-          ## Billing
-          Most billing questions can be answered by referring to either the [Multi-Factor Authentication Pricing page](https://azure.microsoft.com/pricing/details/multi-factor-authentication/) or the documentation for [Azure AD Multi-Factor Authentication versions and consumption plans](concept-mfa-licensing.md).
-
       - question: |
           Does Azure AD Multi-Factor Authentication throttle user sign-ins?
         answer: |
@@ -135,7 +132,7 @@ sections:
       - question: |
           What should I tell my users to do if they don't receive a response on their phone?
         answer: |
-          Have your users attempt up to five times in 5 minutes to get a phone call or SMS for authentication. Microsoft uses multiple providers for delivering calls and SMS messages. If this approach doesn't work, open a support case to troubleshoot further.
+          Have your users attempt up to five times in 5 minutes to get a phone call or text message for authentication. Microsoft uses multiple providers for delivering calls and text messages. If this approach doesn't work, open a support case to troubleshoot further.
           
           Third-party security apps may also block the verification code text message or phone call. If using a third-party security app, try disabling the protection, then request another MFA verification code be sent.
           
@@ -168,7 +165,7 @@ sections:
       - question: |
           My users say that sometimes they don't receive the text message or the verification times out.
         answer: |
-          Delivery of SMS messages aren't guaranteed because there are uncontrollable factors that might affect the reliability of the service. These factors include the destination country or region, the mobile phone carrier, and the signal strength.
+          Delivery of text messages isn't guaranteed because uncontrollable factors might affect the reliability of the service. These factors include the destination country or region, the mobile phone carrier, and the signal strength.
           
           Third-party security apps may also block the verification code text message or phone call. If using a third-party security app, try disabling the protection, then request another MFA verification code be sent.
           

articles/active-directory/authentication/passwords-faq.yml

@@ -95,25 +95,25 @@ sections:
             >
             > Users can attempt to validate their information (such as their phone number), but if they're unable to prove their identity five times within a 24-hour period, they're locked out for 24 hours.
             >
-            > Users can try to validate a phone number, auth app, send a SMS, or validate security questions and answers only five times within an hour before they're locked out for 24 hours. 
+            > Users can try to validate a phone number, auth app, send a text message, or validate security questions and answers only five times within an hour before they're locked out for 24 hours. 
             >
             > Users can send an email a maximum of 10 times within a 10 minute period before they're locked out for 24 hours.
             >
             > The counters are reset once a user resets their password.
             >
             >
       - question: |
-          How long should I wait to receive an email, SMS, or phone call from password reset? 
+          How long should I wait to receive an email, text message, or phone call from password reset? 
         answer: |
-            > Emails, SMS messages, and phone calls should arrive in under a minute. The normal case is 5 to 20 seconds.
+            > Emails, text messages, and phone calls should arrive in under a minute. The normal case is 5 to 20 seconds.
             > If you don't receive the notification in this time frame:
             > * Check your junk folder.
             > * Check that the number or email being contacted is the one you expect.
             > * Check that the authentication data in the directory is correctly formatted, for example, +1 4255551234 or *user\@contoso.com*. 
       - question: |
           What languages are supported by password reset? 
         answer: |
-            > The password reset UI, SMS messages, and voice calls are localized in the same languages that are supported in Microsoft 365.
+            > The password reset UI, text messages, and voice calls are localized in the same languages that are supported in Microsoft 365.
             >
             >
       - question: |
@@ -201,9 +201,9 @@ sections:
             >
             >
       - question: |
-          How long are the email and SMS one-time passcodes valid? 
+          How long are the email and text message one-time passcodes valid? 
         answer: |
-            > The session lifetime for password reset is 15 minutes. From the start of the password reset operation, the user has 15 minutes to reset their password. The email and SMS one-time passcode are valid for 5 minutes during the password reset session.
+            > The session lifetime for password reset is 15 minutes. From the start of the password reset operation, the user has 15 minutes to reset their password. The one-time passcodes are valid for 5 minutes during the password reset session.
             >
             >
       - question: |

articles/active-directory/privileged-identity-management/media/azure-ad-pim-approval-workflow/approve-1.png

@@ -21,6 +21,8 @@ ms.collection: M365-identity-device-management
 
 With Privileged Identity Management (PIM) in Azure Active Directory (Azure AD), part of Microsoft Entra, you can configure roles to require approval for activation, and choose one or multiple users or groups as delegated approvers. Delegated approvers have 24 hours to approve requests. If a request is not approved within 24 hours, then the eligible user must re-submit a new request. The 24 hour approval time window is not configurable.
 
+
+
 ## View pending requests
 
 [!INCLUDE [portal updates](~/articles/active-directory/includes/portal-update.md)]
@@ -96,18 +98,15 @@ GET https://graph.microsoft.com/v1.0/roleManagement/directory/roleAssignmentSche
 >[!NOTE]
 >Approvers are not able to approve their own role activation requests.
 
-1. Find and select the request that you want to approve. An approve or deny page appears.
-
-    ![Screenshot that shows the "Approve requests - Azure AD roles" page.](./media/azure-ad-pim-approval-workflow/resources-approve-pane.png)
-
-1. In the **Justification** box, enter the business justification.
-
-1. Select **Approve**. You will receive an Azure notification of your approval.
-
-    ![Approve notification showing request was approved](./media/pim-resource-roles-approval-workflow/resources-approve-pane.png)
+ 1. Find and select the request that you want to approve. An approve or deny page appears.
+ 2. In the **Justification** box, enter the business justification.
+ 3. Select **Submit**. You will receive an Azure notification of your approval.
 
 ## Approve pending requests using Microsoft Graph API
 
+>[!NOTE]
+> Approval for **extend and renew** requests is currently not supported by the Microsoft Graph API
+
 ### Get IDs for the steps that require approval
 
 For a specific activation request, this command gets all the approval steps that need approval. Multi-step approvals are not currently supported.
@@ -148,8 +147,8 @@ GET https://graph.microsoft.com/beta/roleManagement/directory/roleAssignmentAppr
 PATCH 
 https://graph.microsoft.com/beta/roleManagement/directory/roleAssignmentApprovals/<request-ID-GUID>/steps/<approval-step-ID-GUID> 
 { 
-    "reviewResult": "Approve", 
-    "justification": "abcdefg" 
+    "reviewResult": "Approve", // or "Deny"
+    "justification": "Trusted User" 
 } 
  ````
 
@@ -159,13 +158,9 @@ Successful PATCH calls generate an empty response.
 
 ## Deny requests
 
-1. Find and select the request that you want to deny. An approve or deny page appears.
-
-    ![Approve requests - approve or deny pane with details and Justification box](./media/pim-resource-roles-approval-workflow/resources-approve-pane.png)
-
-1. In the **Justification** box, enter the business justification.
-
-1. Select **Deny**. A notification appears with your denial.
+ 1. Find and select the request that you want to approve. An approve or deny page appears.
+ 2. In the **Justification** box, enter the business justification.
+ 3. Select **Deny**. A notification appears with your denial.
 
 ## Workflow notifications