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
| fragment-id | A string. Policy expression allowed. Specifies the identifier (name) of a policy fragment created in the API Management instance. | Yes | N/A |
31
+
| fragment-id | A string. Specifies the identifier (name) of a policy fragment created in the API Management instance. | Yes | N/A |
32
32
33
33
## Usage
34
34
@@ -52,4 +52,4 @@ In the following example, the policy fragment named *myFragment* is added in the
Copy file name to clipboardExpand all lines: articles/bastion/kerberos-authentication-portal.md
+5-3Lines changed: 5 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,9 +14,11 @@ ms.author: cherylmc
14
14
15
15
This article shows you how to configure Azure Bastion to use Kerberos authentication. Kerberos authentication can be used with both the Basic and the Standard Bastion SKUs. For more information about Kerberos authentication, see the [Kerberos authentication overview](/windows-server/security/kerberos/kerberos-authentication-overview). For more information about Azure Bastion, see [What is Azure Bastion?](bastion-overview.md)
16
16
17
-
> [!NOTE]
18
-
> During Preview, the Kerberos setting for Azure Bastion can be configured in the Azure portal only.
19
-
>
17
+
## Considerations
18
+
19
+
* During Preview, the Kerberos setting for Azure Bastion can be configured in the Azure portal only.
20
+
* VMs migrated from on-premises to Azure are not currently supported for Kerberos.
21
+
* Cross-realm authentication is not currently supported for Kerberos.
Copy file name to clipboardExpand all lines: articles/cosmos-db/mongodb/change-log.md
+7-1Lines changed: 7 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ ms.reviewer: gahllevy
7
7
ms.service: cosmos-db
8
8
ms.subservice: mongodb
9
9
ms.topic: release-notes
10
-
ms.date: 10/12/2022
10
+
ms.date: 01/18/2023
11
11
ms.custom: ignite-2022
12
12
---
13
13
@@ -17,6 +17,12 @@ The Change log for the API for MongoDB is meant to inform you about our feature
17
17
18
18
## Azure Cosmos DB for MongoDB updates
19
19
20
+
### Azure Cosmos DB for MongoDB 5.0 (Limited Preview)
21
+
22
+
The 5.0 version supports many new features such as distributed ACID transactions, higher limits for unsharded collections and for shards themselves, improved performance for aggregation pipelines and complex queries, and more.
23
+
24
+
[Request access today to try out this Limited Preview!](../access-previews.md)
25
+
20
26
### Role-based access control (RBAC) (GA)
21
27
22
28
Azure Cosmos DB for MongoDB now offers a built-in role-based access control (RBAC) that allows you to authorize your data requests with a fine-grained, role-based permission model. Using this role-based access control (RBAC) allows you access with more options for control, security, and auditability of your database account data.
Copy file name to clipboardExpand all lines: articles/machine-learning/how-to-manage-compute-sessions.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ ms.reviewer: sgilley
9
9
ms.service: machine-learning
10
10
ms.subservice: core
11
11
ms.topic: how-to
12
-
ms.date: 12/21/2022
12
+
ms.date: 1/18/2023
13
13
# Customer intent: As a data scientist, I want to manage the notebook and terminal sessions on my compute instance for optimal performance.
14
14
---
15
15
@@ -19,24 +19,24 @@ Notebook and terminal sessions run on the compute and maintain your current work
19
19
20
20
When you reopen a notebook, or reconnect to a terminal session, you can reconnect to the previous session state (including command history, execution history, and defined variables). However, too many active sessions may slow down the performance of your compute. With too many active sessions, you may find your terminal or notebook cell typing lags, or terminal or notebook command execution may feel slower than expected.
21
21
22
-
There's a session management panel in the Azure Machine Learning studio that helps you manage your active sessions and optimize the performance of your compute instance. You can navigate to this session management panel from the compute toolbar of either a terminal tab or a notebook tab.
22
+
Use the session management panel in Azure Machine Learning studio to help you manage your active sessions and optimize the performance of your compute instance. Navigate to this session management panel from the compute toolbar of either a terminal tab or a notebook tab.
23
23
24
24
> [!NOTE]
25
25
> For optimal performance, we recommend you don’t keep more than six active sessions - and the fewer the better.
26
26
27
-
:::image type="content" source="media/how-to-manage-compute-sessions/compute-session-management-panel.png" alt-text="Screenshot of compute session management panel.":::
27
+
:::image type="content" source="media/how-to-manage-compute-sessions/compute-session-management-panel.png" alt-text="Screenshot of compute session management panel." lightbox="media/how-to-manage-compute-sessions/compute-session-management-panel.png":::
28
28
29
29
## Notebook sessions
30
30
31
-
In the session management panel, you can select a linked notebook name in the notebook sessions section to reopen a notebook with its previous state.
31
+
In the session management panel, select a linked notebook name in the notebook sessions section to reopen a notebook with its previous state.
32
32
33
33
Notebook sessions are kept active when you close a notebook tab in the Azure Machine Learning studio. So, when you reopen a notebook you'll have access to previously defined variables and execution state - in this case, you're benefitting from the active notebook session.
34
34
35
35
However, keeping too many active notebook sessions can slow down the performance of your compute. So, you should use the session management panel to shut down any notebook sessions you no longer need.
36
36
37
37
Select **Manage active sessions** in the terminal toolbar to open the session management panel and shut down the sessions you no longer need. In the following image, you can see that the tooltip shows the count of active notebook sessions.
38
38
39
-
:::image type="content" source="media/how-to-manage-compute-sessions/notebook-sessions-button.png" alt-text="Screenshot of notebooks sessions button in toolbar.":::
39
+
:::image type="content" source="media/how-to-manage-compute-sessions/notebook-sessions-button.png" alt-text="Screenshot of notebooks sessions button in toolbar." lightbox="media/how-to-manage-compute-sessions/notebook-sessions-button.png":::
40
40
41
41
## Terminal sessions
42
42
@@ -46,4 +46,4 @@ In contrast to notebook sessions, terminal sessions are terminated when you clos
46
46
47
47
Select **Manage active sessions** in the terminal toolbar to open the session management panel and shut down the sessions you no longer need. In the following image, you can see that the tooltip shows the count of active terminal sessions.
48
48
49
-
:::image type="content" source="media/how-to-manage-compute-sessions/terminal-sessions-button.png" alt-text="Screenshot of terminal sessions button in toolbar.":::
49
+
:::image type="content" source="media/how-to-manage-compute-sessions/terminal-sessions-button.png" alt-text="Screenshot of terminal sessions button in toolbar." lightbox="media/how-to-manage-compute-sessions/terminal-sessions-button.png":::
Copy file name to clipboardExpand all lines: articles/service-health/resource-health-overview.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -63,7 +63,7 @@ Different resources have their own criteria for when they report that they are d
63
63
64
64
65
65
66
-
For virtual machine scale sets, visit [Resource health state is "Degraded" in Azure Virtual Machine Scale Set](/troubleshoot/azure/virtual-machine-scale-sets/resource-health-degraded-state) page for more information.
66
+
For Virtual Machine Scale Sets, visit [Resource health state is "Degraded" in Azure Virtual Machine Scale Set](/troubleshoot/azure/virtual-machine-scale-sets/resource-health-degraded-state) page for more information.
67
67
68
68
## History information
69
69
@@ -85,9 +85,12 @@ To open Resource Health for one resource:
85
85
1. Sign in to the Azure portal.
86
86
2. Browse to your resource.
87
87
3. On the resource menu in the left pane, select **Resource health**.
88
+
4. From the health history grid, you can either download a PDF or click the "Share/Manage" RCA button.
88
89
89
90
90
91
92
+
:::image type="content" source="./media/resource-health-overview/resource-health-history-grid.png" lightbox="./media/resource-health-overview/resource-health-history-grid.png" alt-text="Screenshot of the Resource Health pane in the Azure portal. The Unavailable message and Download as PDF and Share/Manage RCA buttons are highlighted.":::
93
+
91
94
You can also access Resource Health by selecting **All services** and typing **resource health** in the filter text box. In the **Help + support** pane, select [Resource health](https://portal.azure.com/#blade/Microsoft_Azure_Monitoring/AzureMonitoringBrowseBlade/resourceHealth).
92
95
93
96
0 commit comments