Skip to content

Commit 6788bee

Browse files
authored
Merge pull request #103754 from SadiqhAhmed-MSFT/patch-16
(AzureCXP) fixes 47725
2 parents 04a8fb4 + 1d8b3eb commit 6788bee

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/cost-management-billing/manage/spending-limit.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -54,7 +54,7 @@ To remove your spending limit, follow these steps:
5454

5555
The spending limit could prevent you from deploying or using certain third-party and Microsoft services. Here are the situations where you should remove the spending limit on your subscription.
5656

57-
- You plan to deploy first party images like Oracle or services such as Azure DevOps Services. This situation causes you to reach your spending limit almost immediately and causes your subscription to be disabled.
57+
- You plan to deploy third-party images like Oracle or services such as Azure DevOps Services. This situation causes you to reach your spending limit almost immediately and causes your subscription to be disabled.
5858
- You have services that you don't want disrupted. When you reach your spending limit, Azure resources that you deployed are removed from production and your Azure virtual machines are stopped and de-allocated. If you have services that you don't want disrupted, you must remove your spending limit.
5959
- You have services and resources with settings like virtual IP addresses that you don't want to lose. These settings are lost when your reach your spending limit and the services and resources are de-allocated.
6060

0 commit comments

Comments
 (0)