Skip to content

Commit 57dc4d0

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into erlocationupdate
2 parents a320af0 + 9e80f99 commit 57dc4d0

File tree

3 files changed

+24
-7
lines changed

3 files changed

+24
-7
lines changed

articles/azure-functions/create-first-function-cli-python.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Create a Python function from the command line - Azure Functions
33
description: Learn how to create a Python function from the command line, then publish the local project to serverless hosting in Azure Functions.
4-
ms.date: 06/15/2022
4+
ms.date: 03/22/2023
55
ms.topic: quickstart
66
ms.devlang: python
77
ms.custom: devx-track-python, devx-track-azurecli, devx-track-azurepowershell, mode-api, devdivchpfy22
@@ -79,7 +79,7 @@ Verify your prerequisites, which depend on whether you're using Azure CLI or Azu
7979

8080
## <a name="create-venv"></a>Create and activate a virtual environment
8181

82-
In a suitable folder, run the following commands to create and activate a virtual environment named `.venv`. Make sure that you're using Python 3.8, 3.7 or 3.6, which are supported by Azure Functions.
82+
In a suitable folder, run the following commands to create and activate a virtual environment named `.venv`. Make sure that you're using Python 3.9, 3.8, or 3.7, which are supported by Azure Functions.
8383

8484
# [bash](#tab/bash)
8585

@@ -328,15 +328,15 @@ Use the following commands to create these items. Both Azure CLI and PowerShell
328328
az functionapp create --consumption-plan-location westeurope --runtime python --runtime-version 3.9 --functions-version 4 --name <APP_NAME> --os-type linux --storage-account <STORAGE_NAME>
329329
```
330330
331-
The [az functionapp create](/cli/azure/functionapp#az-functionapp-create) command creates the function app in Azure. If you're using Python 3.8, 3.7, or 3.6, change `--runtime-version` to `3.8`, `3.7`, or `3.6`, respectively. You must supply `--os-type linux` because Python functions can't run on Windows, which is the default.
331+
The [az functionapp create](/cli/azure/functionapp#az-functionapp-create) command creates the function app in Azure. If you're using Python 3.9, 3.8, or 3.7, change `--runtime-version` to `3.9`, `3.8`, or `3.7`, respectively. You must supply `--os-type linux` because Python functions can't run on Windows, which is the default.
332332
333333
# [Azure PowerShell](#tab/azure-powershell)
334334
335335
```azurepowershell
336336
New-AzFunctionApp -Name <APP_NAME> -ResourceGroupName AzureFunctionsQuickstart-rg -StorageAccountName <STORAGE_NAME> -FunctionsVersion 4 -RuntimeVersion 3.9 -Runtime python -Location '<REGION>'
337337
```
338338
339-
The [New-AzFunctionApp](/powershell/module/az.functions/new-azfunctionapp) cmdlet creates the function app in Azure. If you're using Python 3.8, 3.7, or 3.6, change `-RuntimeVersion` to `3.8`, `3.7`, or `3.6`, respectively.
339+
The [New-AzFunctionApp](/powershell/module/az.functions/new-azfunctionapp) cmdlet creates the function app in Azure. If you're using Python 3.9, 3.8, or 3.7, change `-RuntimeVersion` to `3.9`, `3.8`, or `3.7`, respectively.
340340
341341
---
342342

articles/cdn/cdn-custom-ssl.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -123,8 +123,9 @@ Register Azure CDN as an app in your Azure Active Directory via PowerShell.
123123
`New-AzADServicePrincipal -ApplicationId "205478c0-bd83-4e1b-a9d6-db63a3e1e1c8" -Role Contributor`
124124

125125
> [!NOTE]
126-
> * **205478c0-bd83-4e1b-a9d6-db63a3e1e1c8** is the service principal for **Microsoft.AzureFrontDoor-Cdn**.
126+
> * `205478c0-bd83-4e1b-a9d6-db63a3e1e1c8` is the service principal for `Microsoft.AzureFrontDoor-Cdn`.
127127
> * You need to have the **Global Administrator** role to run this command.
128+
> * The service principal name was changed from `Microsoft.Azure.Cdn` to `Microsoft.AzureFrontDoor-Cdn`.
128129
129130
```bash
130131
New-AzADServicePrincipal -ApplicationId "205478c0-bd83-4e1b-a9d6-db63a3e1e1c8" -Role Contributor

articles/storage/files/storage-files-identity-auth-azure-active-directory-enable.md

Lines changed: 18 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn how to enable identity-based Kerberos authentication for hybr
44
author: khdownie
55
ms.service: storage
66
ms.topic: how-to
7-
ms.date: 12/05/2022
7+
ms.date: 03/22/2023
88
ms.author: kendownie
99
ms.subservice: files
1010
ms.custom: engagement-fy23
@@ -152,7 +152,7 @@ After enabling Azure AD Kerberos authentication, you'll need to explicitly grant
152152

153153
4. Select the application with the name matching **[Storage Account] `<your-storage-account-name>`.file.core.windows.net**.
154154
5. Select **API permissions** in the left pane.
155-
6. Select **Grant admin consent for "DirectoryName"**.
155+
6. Select **Grant admin consent**.
156156
7. Select **Yes** to confirm.
157157

158158
## Disable multi-factor authentication on the storage account
@@ -202,6 +202,22 @@ Use one of the following three methods:
202202

203203
Changes are not instant, and require a policy refresh or a reboot to take effect.
204204

205+
> [!IMPORTANT]
206+
> Once this change is applied, the client(s) won't be able to connect to storage accounts that are configured for on-premises AD DS integration without configuring Kerberos realm mappings. If you want the client(s) to be able to connect to storage accounts configured for AD DS as well as storage accounts configured for Azure AD Kerberos, follow the steps in [Configure coexistence with storage accounts using on-premises AD DS](#configure-coexistence-with-storage-accounts-using-on-premises-ad-ds).
207+
208+
### Configure coexistence with storage accounts using on-premises AD DS
209+
210+
If you want to enable client machines to connect to storage accounts that are configured for AD DS as well as storage accounts configured for Azure AD Kerberos, follow these steps. If you're only using Azure AD Kerberos, skip this section.
211+
212+
Add an entry for each storage account that uses on-premises AD DS integration. Use one of the following three methods to configure Kerberos realm mappings:
213+
214+
- Configure this Intune [Policy CSP](/windows/client-management/mdm/policy-configuration-service-provider) and apply it to the client(s): [Kerberos/HostToRealm](/windows/client-management/mdm/policy-csp-admx-kerberos#hosttorealm)
215+
- Configure this group policy on the client(s): `Administrative Template\System\Kerberos\Define host name-to-Kerberos realm mappings`
216+
- Configure the following registry value on the client(s): `reg add HKLM\SYSTEM\CurrentControlSet\Control\Lsa\Kerberos\domain_realm /v <DomainName> /d <StorageAccountEndPoint>`
217+
- For example, `reg add HKLM\SYSTEM\CurrentControlSet\Control\Lsa\Kerberos\domain_realm /v contoso.local /d <your-storage-account-name>.file.core.windows.net`
218+
219+
Changes are not instant, and require a policy refresh or a reboot to take effect.
220+
205221
## Disable Azure AD authentication on your storage account
206222

207223
If you want to use another authentication method, you can disable Azure AD authentication on your storage account by using the Azure portal, Azure PowerShell, or Azure CLI.

0 commit comments

Comments
 (0)