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: support/azure/virtual-machines/windows/allocation-failure.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -228,12 +228,12 @@ Reduce the number of instances of the requested VM size, and then retry the depl
228
228
229
229
The servers in Azure datacenters are partitioned into clusters. Normally, an allocation request is attempted in multiple clusters, but it's possible that certain constraints (such as VM size, Ultra SSD, and proximity placement groups) from the allocation request force the Azure platform to attempt the request in only one cluster. The following Diagram 1 illustrates the case of a normal allocation that's attempted in multiple clusters.
230
230
231
-
:::image type="content" source="media/virtual-machines-common-allocation-failure/how-allocation-works.svg" alt-text="Screenshot of Diagram 1 showing allocation attempted in multiple clusters." lightbox="media/virtual-machines-common-allocation-failure/how-allocation-works.svg":::
231
+
:::image type="content" source="media/virtual-machines-common-allocation-failure/how-allocation-works.png" alt-text="Screenshot of Diagram 1 showing allocation attempted in multiple clusters." lightbox="media/virtual-machines-common-allocation-failure/how-allocation-works.png":::
232
232
233
233
### Why allocation failures happen
234
234
235
235
When an allocation has a large number of restrictions, there's a higher chance of failing to find free resources since the available resource pool is smaller. Furthermore, if your allocation request is restricted (for example, when using proximity placement groups but the type of resource you requested isn’t supported by the set of clusters and nearby ones), your request fails even if the cluster has free resources. The following Diagram 2 illustrates the case where an allocation fails because the candidate clusters associated with the proximity placement group don't have free resources. Diagram 3 illustrates the case where an allocation fails because the candidate clusters associated with the proximity placement group don’t support the requested VM size, even though the clusters have free resources.
236
236
237
-
:::image type="content" source="media/virtual-machines-common-allocation-failure/allocation-failures-ppg.svg" alt-text="Screenshot of Diagram 2 showing allocation failed with no free resource available and Diagram 3 showing allocation failed with size not supported." lightbox="media/virtual-machines-common-allocation-failure/allocation-failures-ppg.svg":::
237
+
:::image type="content" source="media/virtual-machines-common-allocation-failure/allocation-failures-ppg.png" alt-text="Screenshot of Diagram 2 showing allocation failed with no free resource available and Diagram 3 showing allocation failed with size not supported." lightbox="media/virtual-machines-common-allocation-failure/allocation-failures-ppg.png":::
238
238
239
239
[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]
Copy file name to clipboardExpand all lines: support/azure/virtual-machines/windows/media/virtual-machines-common-allocation-failure/allocation-failures-ppg.svg
Copy file name to clipboardExpand all lines: support/azure/virtual-machines/windows/media/virtual-machines-common-allocation-failure/how-allocation-works.svg
Copy file name to clipboardExpand all lines: support/power-platform/dataverse/d365-app-outlook/attachments-not-tracked-to-dynamics-365-after-office-365-atp-is-enabled.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,6 +3,7 @@ title: Attachments not tracked after Defender for Office 365 is enabled
3
3
description: This article resolves an issue where attachments aren't tracked to Microsoft Dynamics 365 after Microsoft Defender for Office 365 is enabled.
4
4
ms.reviewer: dmartens, Chris.Davis
5
5
ms.date: 03/06/2023
6
+
ms.custom: sap:Dynamics 365 App for Outlook Add-In
6
7
---
7
8
# Attachments aren't tracked to Microsoft Dynamics 365 after Microsoft Defender for Office 365 is enabled
Copy file name to clipboardExpand all lines: support/power-platform/dataverse/d365-app-outlook/cannot-connect-to-exchange-message-when-using-dynamics-365-app-for-outlook.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,6 +4,7 @@ description: When you use Microsoft Dynamics 365 App for Outlook, you receive a
4
4
ms.reviewer:
5
5
ms.topic: troubleshooting
6
6
ms.date: 03/31/2021
7
+
ms.custom: sap:Dynamics 365 App for Outlook Add-In
7
8
---
8
9
# Can't connect to Exchange message appears when using Microsoft Dynamics 365 App for Outlook
0 commit comments