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/billing/billing-how-to-change-azure-account-profile.md
+7-1Lines changed: 7 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -81,11 +81,17 @@ To opt out of receiving marketing emails:
81
81
1. Go to the [request form](https://account.microsoft.com/profile/permissions-link-request) to submit a request by using your profile email address. You'll receive a link by email to update your preferences.
82
82
2. Select the link to open the **Manage communication permissions** page. This page shows you the types of marketing communications that the email address is opted in to. Clear any topics that you want to opt out of, and then select **Save**.
83
83
84
-
85
84

86
85
87
86
When you opt out of marketing communications, you still receive service notifications, based on your account.
88
87
88
+
## Change the subscription name
89
+
90
+
1. Sign in to the [Azure portal](https://portal.azure.com), select **Subscription** from the left pane, and then select the subscription that you want to rename.
91
+
1. Select **Overview**, and then select **Rename** from the command bar.
92
+

93
+
1. After you have changed the name, select **Save**.
94
+
89
95
## Need help? Contact us.
90
96
91
97
If you have questions or need help, [create a support request](https://go.microsoft.com/fwlink/?linkid=2083458).
@@ -88,30 +87,27 @@ For the VM that is created from a custom image, you must configure the appropria
88
87
89
88
4. Verify by using Psping that you have connectivity to the KMS server. Switch to the folder where you extracted the Pstools.zip download, and then run the following:
90
89
91
-
92
90
```
93
91
\psping.exe kms.core.windows.net:1688
94
92
```
95
-
96
-
97
93
In the second-to-last line of the output, make sure that you see: Sent = 4, Received = 4, Lost = 0 (0% loss).
98
94
99
95
If Lost is greater than 0 (zero), the VM does not have connectivity to the KMS server. In this situation, if the VM is in a virtual network and has a custom DNS server specified, you must make sure that DNS server is able to resolve kms.core.windows.net. Or, change the DNS server to one that does resolve kms.core.windows.net.
100
96
101
97
Notice that if you remove all DNS servers from a virtual network, VMs use Azure’s internal DNS service. This service can resolve kms.core.windows.net.
102
98
103
-
Also verify that the guest firewall has not been configured in a manner that would block activation attempts.
99
+
Also make sure that the outbound network traffic to KMS endpoint with 1688 port is not blocked by the firewall in the VM.
104
100
105
-
1. After you verify successful connectivity to kms.core.windows.net, run the following command at that elevated Windows PowerShell prompt. This command tries activation multiple times.
101
+
5. After you verify successful connectivity to kms.core.windows.net, run the following command at that elevated Windows PowerShell prompt. This command tries activation multiple times.
0 commit comments