You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/reliability/reliability-functions.md
+14-6Lines changed: 14 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -126,6 +126,8 @@ There are currently multiple ways to deploy a zone-redundant Flex Consumption ap
126
126
127
127
#### [Azure portal](#tab/azure-portal)
128
128
129
+
1. To create a function app in a zone-redundant plan, you must have an existing [zone-redundant storage account](../azure-functions/storage-considerations.md#storage-account-requirements). If you don't already have a zone-redundant storage account, create one before you proceed.
130
+
129
131
1. In the Azure portal, go to the **Create Function App** page. For more information about creating a function app in the portal, see [Create a function app](../azure-functions/functions-create-function-app-portal.md#create-a-function-app).
130
132
131
133
1. Select **Flex Consumption** and then select the **Select** button.
@@ -140,7 +142,7 @@ There are currently multiple ways to deploy a zone-redundant Flex Consumption ap
140
142
:::image type="content" source="../azure-functions/media/functions-az-redundancy/azure-functions-flex-basics-az.png" alt-text="Screenshot of the Basics tab of the Flex Consumption function app create page.":::
141
143
142
144
143
-
1. On the **Storage** tab, enter the settings for your function app storage account. Pay special attention to the setting in the following table, which has specific requirements for zone redundancy.
145
+
1. On the **Storage** tab, select the zone-redundant storage account for your function app. Pay special attention to the setting in the following table, which has specific requirements for zone redundancy.
144
146
145
147
| Setting | Suggested value | Notes for zone redundancy |
146
148
| ------------ | ---------------- | ----------- |
@@ -240,21 +242,27 @@ After the storage accounts used by your app are updated, you can update the Flex
240
242
241
243
#### [Azure portal](#tab/azure-portal)
242
244
243
-
Not currently supported.
245
+
1. In the Azure portal, search for and select the function app to update.
246
+
247
+
1. Under **Settings**, select **Scale and Concurrency**.
248
+
249
+
1. On the **Zone redundancy** tab, check **Add zone redundancy** to enable the feature. If already checked, you can uncheck this box to disable the feature.
250
+
251
+
1. Select **Save** to commit your changes and restart the app.
252
+
253
+
:::image type="content" source="../azure-functions/media/functions-az-redundancy/azure-functions-flex-update-az.png" alt-text="Screenshot of the Scale and Concurrency tab of a Flex Consumption function app.":::
244
254
245
255
#### [Azure CLI](#tab/azure-cli)
246
256
247
-
Not currently supported.
248
-
<!--- unhide this after we get the required CLI fix implemented
249
-
Update the Flex Consumption app by using the [az functionapp plan update](/cli/azure/functionapp#az-functionapp-plan-update) command and setting the `--zone-redundant true` parameter:
257
+
Update the app by using the `--zone-redundant` parameter of the [az functionapp plan update](/cli/azure/functionapp/plan#az-functionapp-plan-update) command. Use a value of `true` to enable zone redundancy and `false` disable the feature. This example enables zone redundancy for an existing app in a Flex Consumption plan:
Copy file name to clipboardExpand all lines: articles/sentinel/work-with-threat-indicators.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -247,7 +247,7 @@ There's also a rich resource for [Azure Monitor workbooks on GitHub](https://git
247
247
248
248
## Export threat intelligence
249
249
250
-
Microsoft Sentinel lets you export threat intelligence from to other destinations. For example, if you've ingested threat intelligence using the **Threat Intelligence - TAXII** data connector, you can export threat intelligence back to the source platform for bi-directional intelligence sharing. The export feature reduces the need for manual processes or custom playbooks to distribute threat intelligence.
250
+
Microsoft Sentinel lets you export threat intelligence to other destinations. For example, if you've ingested threat intelligence using the **Threat Intelligence - TAXII** data connector, you can export threat intelligence back to the source platform for bi-directional intelligence sharing. The export feature reduces the need for manual processes or custom playbooks to distribute threat intelligence.
251
251
252
252
> [!IMPORTANT]
253
253
> Carefully consider both the threat intelligence data you export and its destination, which might reside in a different geographic or regulatory region. Data export cannot be undone. Ensure you own the data or have proper authorization before exporting or sharing threat intelligence with third parties.
0 commit comments