Skip to content

Commit f847910

Browse files
authored
Merge pull request #233659 from MicrosoftDocs/main
4/06 AM Publish
2 parents 9934085 + ce56291 commit f847910

30 files changed

+219
-149
lines changed

articles/active-directory/app-provisioning/on-premises-scim-provisioning.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -42,10 +42,10 @@ Once the agent is installed, no further configuration is necesary on-prem, and a
4242
4. Select the agent that you installed from the dropdown list and select **Assign Agent(s)**.
4343
5. Now either wait 10 minutes or restart the **Microsoft Azure AD Connect Provisioning Agent** before proceeding to the next step & testing the connection.
4444
6. In the **Tenant URL** field, provide the SCIM endpoint URL for your application. The URL is typically unique to each target application and must be resolveable by DNS. An example for a scenario where the agent is installed on the same host as the application is https://localhost:8585/scim ![Screenshot that shows assigning an agent.](./media/on-premises-scim-provisioning/scim-2.png)
45-
>[!NOTE]
46-
>The Azure AD provisioning service currently drops everything in the URL after the hostname.
47-
4845
7. Select **Test Connection**, and save the credentials. The application SCIM endpoint must be actively listening for inbound provisioning requests, otherwise the test will fail. Use the steps [here](on-premises-ecma-troubleshoot.md#troubleshoot-test-connection-issues) if you run into connectivity issues.
46+
>[!NOTE]
47+
> If the test connection fails, you will see the request made. Please note that while the URL in the test connection error message is truncated, the actual request sent to the aplication contains the entire URL provided above.
48+
4949
8. Configure any [attribute mappings](customize-application-attributes.md) or [scoping](define-conditional-rules-for-provisioning-user-accounts.md) rules required for your application.
5050
9. Add users to scope by [assigning users and groups](../../active-directory/manage-apps/add-application-portal-assign-users.md) to the application.
5151
10. Test provisioning a few users [on demand](provision-on-demand.md).

articles/active-directory/authentication/concept-certificate-based-authentication-technical-deep-dive.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -95,7 +95,7 @@ If CBA enabled user cannot use MF cert (such as on mobile device without smart c
9595
## MFA with Single-factor certificate-based authentication
9696

9797
Azure AD CBA can be used as a second factor to meet MFA requirements with single-factor certificates.
98-
Some of the supported combintaions are
98+
Some of the supported combinations are
9999

100100
1. CBA (first factor) + passwordless phone sign-in (PSI as second factor)
101101
1. CBA (first factor) + FIDO2 security keys (second factor)

articles/active-directory/external-identities/azure-ad-account.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ Azure Active Directory is available as an identity provider option for B2B colla
2222

2323
## Guest sign-in using Azure Active Directory accounts
2424

25-
Azure Active Directory is available in the list of External Identities identity providers by default. No further configuration is needed to allow guest users to sign in with their Azure AD account using either the invitation flow or a self-service sign-up user flow.
25+
If you want to enable guest users to sign in with their Azure AD account, you can use either the invitation flow or a self-service sign-up user flow. No additional configuration is required.
2626

2727
:::image type="content" source="media/azure-ad-account/azure-ad-account-identity-provider.png" alt-text="Screenshot of Azure AD account in the identity provider list." lightbox="media/azure-ad-account/azure-ad-account-identity-provider.png":::
2828

articles/active-directory/fundamentals/concept-secure-remote-workers.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ This guide assumes that your cloud only or hybrid identities have been establish
3434

3535
### Guided walkthrough
3636

37-
For a guided walkthrough of many of the recommendations in this article, see the [Set up Azure AD](https://go.microsoft.com/fwlink/?linkid=2221308) guide.
37+
For a guided walkthrough of many of the recommendations in this article, see the [Set up Azure AD](https://go.microsoft.com/fwlink/?linkid=2224193) guide when signed in to the Microsoft 365 Admin Center. To review best practices without signing in and activating automated setup features, go to the [M365 Setup portal](https://go.microsoft.com/fwlink/?linkid=2221308).
3838

3939
## Guidance for Azure AD Free, Office 365, or Microsoft 365 customers.
4040

articles/active-directory/reports-monitoring/howto-use-recommendations.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -72,6 +72,9 @@ Each recommendation provides the same set of details that explain what the recom
7272

7373
- The **Impacted resources** table contains a list of resources identified by the recommendation. The resource's name, ID, date it was first detected, and status are provided. The resource could be an application or resource service principal, for example.
7474

75+
> [!NOTE]
76+
> In the Azure portal the impacted resources are limited to a maximum of 50 resources. To view more resources, you should use the expand query parameter at the end of your API query on Microsoft graph. For example: Get: https://graph.microsoft.com/beta/directory/recommendations?$expand=impactedResources
77+
7578
## How to update a recommendation
7679

7780
To update the status of a recommendation or a related resource, sign in to Azure using a least-privileged role for updating a recommendation.
@@ -136,4 +139,4 @@ For more information, see the [Microsoft Graph documentation for recommendations
136139
## Next steps
137140
138141
- [Review the Azure AD recommendations overview](overview-recommendations.md)
139-
- [Learn about Service Health notifications](overview-service-health-notifications.md)
142+
- [Learn about Service Health notifications](overview-service-health-notifications.md)

articles/app-service/app-service-undelete.md

Lines changed: 34 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Restore deleted apps
33
description: Learn how to restore a deleted app in Azure App Service. Avoid the headache of an accidentally deleted app.
44
author: seligj95
55
ms.author: jordanselig
6-
ms.date: 11/4/2022
6+
ms.date: 4/3/2023
77
ms.topic: article
88
ms.custom: devx-track-azurepowershell
99
---
@@ -14,8 +14,8 @@ If you happened to accidentally delete your app in Azure App Service, you can re
1414

1515
> [!NOTE]
1616
> - Deleted apps are purged from the system 30 days after the initial deletion. After an app is purged, it can't be recovered.
17-
> - Undelete functionality isn't supported for the Consumption plan.
18-
> - Apps Service apps running in an App Service Environment don't support snapshots. Therefore, undelete functionality and clone functionality aren't supported for App Service apps running in an App Service Environment.
17+
> - Undelete functionality isn't supported for function apps hosted on the Consumption plan or Elastic Premium plan.
18+
> - App Service apps running in an App Service Environment don't support snapshots. Therefore, undelete functionality and clone functionality aren't supported for App Service apps running in an App Service Environment.
1919
>
2020
2121
## Re-register App Service resource provider
@@ -49,12 +49,12 @@ The detailed information includes:
4949
## Restore deleted app
5050

5151
>[!NOTE]
52-
>- `Restore-AzDeletedWebApp` isn't supported for function apps.
52+
>- `Restore-AzDeletedWebApp` isn't supported for function apps hosted on the Consumption plan or Elastic Premium plan.
5353
>- The Restore-AzDeletedWebApp cmdlet restores a deleted web app. The web app specified by TargetResourceGroupName, TargetName, and TargetSlot will be overwritten with the contents and settings of the deleted web app. If the target parameters are not specified, they will automatically be filled with the deleted web app's resource group, name, and slot. If the target web app does not exist, it will automatically be created in the app service plan specified by TargetAppServicePlanName.
5454
>- By default `Restore-AzDeletedWebApp` will restore both your app configuration as well any content. If you want to only restore content, you use the **`-RestoreContentOnly`** flag with this commandlet.
5555
5656

57-
Once the app you want to restore has been identified, you can restore it using `Restore-AzDeletedWebApp`, please see below examples
57+
After identifying the app you want to restore, you can restore it using `Restore-AzDeletedWebApp`, as shown in the following examples.
5858
>*You can find the full commandlet reference here: **[Restore-AzDeletedWebApp](/powershell/module/az.websites/restore-azdeletedwebapp)*** .
5959
6060
>Restore to the original app name:
@@ -90,16 +90,43 @@ Restore-AzDeletedWebApp -ResourceGroupName <original_rg> -Name <original_app> -D
9090

9191
The inputs for command are:
9292

93-
- **Target Resource Group**: Target resource group where the app will be restored
93+
- **Target Resource Group**: Target resource group where the app is to be restored
9494
- **TargetName**: Target app for the deleted app to be restored to
9595
- **TargetAppServicePlanName**: App Service plan linked to the app
9696
- **Name**: Name for the app, should be globally unique.
9797
- **ResourceGroupName**: Original resource group for the deleted app
9898
- **Slot**: Slot for the deleted app
99-
- **RestoreContentOnly**: By default `Restore-AzDeletedWebApp` will restore both your app configuration as well any content. If you want to only restore content, you can use the `-RestoreContentOnly` flag with this commandlet.
99+
- **RestoreContentOnly**: By default `Restore-AzDeletedWebApp` restores both your app configuration as well any content. If you want to only restore content, you can use the `-RestoreContentOnly` flag with this commandlet.
100100

101101
> [!NOTE]
102102
> If the app was hosted on and then deleted from an App Service Environment, it can be restored only if the corresponding App Service Environment still exists.
103103
104+
## Restore deleted function app
105+
106+
If the function app was hosted on a **Dedicated app service plan**, it can be restored, as long as it was using the default App Service storage.
107+
108+
1. Fetch the DeletedSiteId of the app version you want to restore, using Get-AzDeletedWebApp cmdlet:
109+
110+
```powershell
111+
Get-AzDeletedWebApp -ResourceGroupName <RGofDeletedApp> -Name <NameofApp>
112+
```
113+
2. Create a new function app in a Dedicated plan. Refer to the instructions for [how to create an app in the portal](../azure-functions/functions-create-function-app-portal.md#create-a-function-app).
114+
3. Restore to the newly created function app using this cmdlet:
115+
116+
```powershell
117+
Restore-AzDeletedWebApp -ResourceGroupName <RGofnewapp> -Name <newApp> -deletedId "/subscriptions/xxxx/providers/Microsoft.Web/locations/xxxx/deletedSites/xxxx"
118+
```
119+
120+
Currently there's no support for Undelete (Restore-AzDeletedWebApp) Function app that's hosted in a Consumption plan or Elastic premium plan since the content resides on Azure Files in a Storage account. If you haven't 'hard' deleted that Azure Files storage account, or if the account exists and file shares haven't been deleted, then you may use the steps as workaround:
121+
122+
123+
1. Create a new function app in a Consumption or Premium plan. Refer the instructions for [how to create an app in the portal](../azure-functions/functions-create-function-app-portal.md#create-a-function-app).
124+
2. Set the following [app settings](../azure-functions/functions-how-to-use-azure-function-app-settings.md?tabs=portal#settings) to refer to the old storage account , which contains the content from the previous app.
125+
126+
| App Setting | Suggested value |
127+
| ------------ | ---------------- |
128+
| **AzureWebJobsStorage** | Connection String for the storage account used by the deleted app. |
129+
| **WEBSITE_CONTENTAZUREFILECONNECTIONSTRING** | Connection String for the storage account used by the deleted app. |
130+
| **WEBSITE_CONTENTSHARE** | File share on storage account used by the deleted app. |
104131

105132

articles/azure-functions/functions-networking-options.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -283,6 +283,15 @@ The following APIs let you programmatically manage regional virtual network inte
283283
+ **Azure CLI**: Use the [`az functionapp vnet-integration`](/cli/azure/functionapp/vnet-integration) commands to add, list, or remove a regional virtual network integration.
284284
+ **ARM templates**: Regional virtual network integration can be enabled by using an Azure Resource Manager template. For a full example, see [this Functions quickstart template](https://azure.microsoft.com/resources/templates/function-premium-vnet-integration/).
285285

286+
## Testing
287+
288+
When testing functions in a function app with private endpoints, you must do your testing from within the same virtual network, such as on a virtual machine (VM) in that network. To use the **Code + Test** option in the portal from that VM, you need to add following [CORS origins](./functions-how-to-use-azure-function-app-settings.md?tabs=portal#cors) to your function app:
289+
290+
* https://functions-next.azure.com
291+
* https://functions-staging.azure.com
292+
* https://functions.azure.com
293+
* https://portal.azure.com
294+
286295
## Troubleshooting
287296

288297
[!INCLUDE [app-service-web-vnet-troubleshooting](../../includes/app-service-web-vnet-troubleshooting.md)]

articles/azure-monitor/app/ip-collection.md

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Application Insights IP address collection | Microsoft Docs
33
description: Understand how Application Insights handles IP addresses and geolocation.
44
ms.topic: conceptual
5-
ms.date: 11/15/2022
5+
ms.date: 04/06/2023
66
ms.custom: devx-track-js
77
ms.reviewer: saars
88
---
@@ -126,6 +126,16 @@ Content-Length: 54
126126
}
127127
```
128128
129+
### Powershell
130+
131+
The Powershell 'Update-AzApplicationInsights' cmdlet can disable IP masking with the `DisableIPMasking` parameter.
132+
133+
```powershell
134+
Update-AzApplicationInsights -Name "aiName" -ResourceGroupName "rgName" -DisableIPMasking $false
135+
```
136+
137+
For more information on the 'Update-AzApplicationInsights' cmdlet, see [Update-AzApplicationInsights](https://learn.microsoft.com/powershell/module/az.applicationinsights/update-azapplicationinsights)
138+
129139
## Telemetry initializer
130140

131141
If you need a more flexible alternative than `DisableIpMasking`, you can use a [telemetry initializer](./api-filtering-sampling.md#addmodify-properties-itelemetryinitializer) to copy all or part of the IP address to a custom field. The code for this class is the same across .NET versions.

articles/azure-monitor/app/migrate-from-instrumentation-keys-to-connection-strings.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Migrate from Application Insights instrumentation keys to connection strings
33
description: Learn the steps required to upgrade from Azure Monitor Application Insights instrumentation keys to connection strings.
44
ms.topic: conceptual
5-
ms.date: 02/14/2022
5+
ms.date: 05/06/2023
66
ms.reviewer: cogoodson
77
---
88

articles/azure-monitor/app/worker-service.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -569,7 +569,7 @@ This section provides answers to common questions.
569569

570570
| .NET Core app scenario | Package |
571571
|---------|---------|
572-
| Without HostedServices | AspNetCore |
572+
| Without HostedServices | WorkerService |
573573
| With HostedServices | AspNetCore (not WorkerService) |
574574
| With HostedServices, monitoring only HostedServices | WorkerService (rare scenario) |
575575

0 commit comments

Comments
 (0)