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/active-directory-b2c/active-directory-b2c-ui-customization-custom.md
+3
Original file line number
Diff line number
Diff line change
@@ -48,6 +48,9 @@ Create HTML content with your product's brand name in the title.
48
48
49
49
2. Paste the copied snippet in a text editor, and then save the file as *customize-ui.html*.
50
50
51
+
> [!NOTE]
52
+
> HTML form elements will be removed due to security restrictions if you use login.microsoftonline.com. Please use b2clogin.com if you want to use HTML form elements in your custom HTML content. See [Use b2clogin.com](b2clogin.md) for other benefits.
Copy file name to clipboardExpand all lines: articles/active-directory-b2c/b2clogin.md
+4-1
Original file line number
Diff line number
Diff line change
@@ -17,12 +17,15 @@ ms.subservice: B2C
17
17
18
18
When you set up an identity provider for sign-up and sign-in in your Azure Active Directory (Azure AD) B2C application, you need to specify a redirect URL. In the past, login.microsoftonline.com was used, now you should be using b2clogin.com.
19
19
20
+
> [!NOTE]
21
+
> You can use JavaScript client-side code (currently in preview) in b2clogin.com. Your JavaScript code will be removed from your custom page if you use login.microsoftonline.com. Additional security restrictions are also applied to login.microsoftonline.com, such as removing HTML form elements from your custom page.
22
+
20
23
Using b2clogin.com gives you additional benefits, such as:
21
24
22
25
- Space consumed in the cookie header by Microsoft services is reduced.
23
26
- Your URLs no longer include a reference to Microsoft. For example, `https://your-tenant-name.b2clogin.com/tenant-id/oauth2/authresp`.
24
27
25
-
>[!NOTE]
28
+
>[!NOTE]
26
29
> You can use both the tenant name and the tenant GUID as follows:
27
30
> *`https://your-tenant-name.b2clogin.com/your-tenant-name.onmicrosoft.com` (which still refers to `onmicrosoft.com`)
28
31
> *`https://your-tenant-name.b2clogin.com/your-tenant-guid` (in which case there is no reference to Microsoft at all)
Copy file name to clipboardExpand all lines: articles/active-directory/saas-apps/slack-provisioning-tutorial.md
+3-1
Original file line number
Diff line number
Diff line change
@@ -117,7 +117,9 @@ For more information on how to read the Azure AD provisioning logs, see [Reporti
117
117
118
118
* Only updates if these two settings are configured in Slack's workplace/organization - **Profile syncing is enabled** and **Users cannot change their display name**.
119
119
120
-
* Slack's **userName** attribute has to be under 21 characters and have a unique value.
120
+
* Slack's **userName** attribute has to be under 21 characters and have a unique value.
121
+
122
+
* Slack only allows matching with the attributes **userName** and **email**.
Copy file name to clipboardExpand all lines: articles/aks/ssh.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -35,7 +35,7 @@ To configure your virtual machine scale set-based for SSH access, find the name
35
35
Use the [az aks show][az-aks-show] command to get the resource group name of your AKS cluster, then the [az vmss list][az-vmss-list] command to get the name of your scale set.
36
36
37
37
```azurecli-interactive
38
-
CLUSTER_RESOURCE_GROUP=$(az aks show --resource-group myResourceGroup --name myAKSCluster --query nodeResourceGroup -o tsv)
38
+
$CLUSTER_RESOURCE_GROUP=$(az aks show --resource-group myResourceGroup --name myAKSCluster --query nodeResourceGroup -o tsv)
39
39
SCALE_SET_NAME=$(az vmss list --resource-group $CLUSTER_RESOURCE_GROUP --query [0].name -o tsv)
40
40
```
41
41
@@ -92,7 +92,7 @@ To configure your virtual machine availability set-based AKS cluster for SSH acc
92
92
Use the [az aks show][az-aks-show] command to get the resource group name of your AKS cluster, then the [az vm list][az-vm-list] command to list the virtual machine name of your cluster's Linux node.
93
93
94
94
```azurecli-interactive
95
-
CLUSTER_RESOURCE_GROUP=$(az aks show --resource-group myResourceGroup --name myAKSCluster --query nodeResourceGroup -o tsv)
95
+
$CLUSTER_RESOURCE_GROUP=$(az aks show --resource-group myResourceGroup --name myAKSCluster --query nodeResourceGroup -o tsv)
96
96
az vm list --resource-group $CLUSTER_RESOURCE_GROUP -o table
Copy file name to clipboardExpand all lines: articles/api-management/api-management-howto-disaster-recovery-backup-restore.md
+1
Original file line number
Diff line number
Diff line change
@@ -172,6 +172,7 @@ Note the following constraints when making a backup request:
172
172
- While backup is in progress, **avoid changes in service management** such as SKU upgrade or downgrade, change in domain name, and more.
173
173
- Restore of a **backup is guaranteed only for 30 days** since the moment of its creation.
174
174
-**Usage data** used for creating analytics reports **isn't included** in the backup. Use [Azure API Management REST API][azure api management rest api] to periodically retrieve analytics reports for safekeeping.
175
+
- In addition, the following items are not part of the backup data: custom domain SSL certificates and any intermediate or root certificates uploaded by customer, developer portal content, and virtual network integration settings.
175
176
- The frequency with which you perform service backups affect your recovery point objective. To minimize it, we recommend implementing regular backups and performing on-demand backups after you make changes to your API Management service.
176
177
-**Changes** made to the service configuration, (for example, APIs, policies, and developer portal appearance) while backup operation is in process **might be excluded from the backup and will be lost**.
177
178
-**Allow** access from control plane to Azure Storage Account. Customer should open the following set of Inbound IPs on their Storage Account for Backup.
The _pricing tier_ of an App Service plan determines what App Service features you get and how much you pay for the plan. There are a few categories of pricing tiers:
34
34
35
35
-**Shared compute**: **Free** and **Shared**, the two base tiers, runs an app on the same Azure VM as other App Service apps, including apps of other customers. These tiers allocate CPU quotas to each app that runs on the shared resources, and the resources cannot scale out.
36
36
-**Dedicated compute**: The **Basic**, **Standard**, **Premium**, and **PremiumV2** tiers run apps on dedicated Azure VMs. Only apps in the same App Service plan share the same compute resources. The higher the tier, the more VM instances are available to you for scale-out.
37
-
-**Isolated**: This tier runs dedicated Azure VMs on dedicated Azure Virtual Networks, which provides network isolation on top of compute isolation to your apps. It provides the maximum scale-out capabilities.
38
-
-**Consumption**: This tier is only available to [function apps](../azure-functions/functions-overview.md). It scales the functions dynamically depending on workload. For more information, see [Azure Functions hosting plans comparison](../azure-functions/functions-scale.md).
37
+
-**Isolated**: This tier runs dedicated Azure VMs on dedicated Azure Virtual Networks. It provides network isolation on top of compute isolation to your apps. It provides the maximum scale-out capabilities.
@@ -75,9 +74,8 @@ This section describes how App Service apps are billed. For detailed, region-spe
75
74
Except for **Free** tier, an App Service plan carries an hourly charge on the compute resources it uses.
76
75
77
76
- In the **Shared** tier, each app receives a quota of CPU minutes, so _each app_ is charged hourly for the CPU quota.
78
-
- In the dedicated compute tiers (**Basic**, **Standard**, **Premium**, **PremiumV2**), The App Service plan defines the number of VM instances the apps are scaled to, so _each VM instance_ in the App Service plan has an hourly charge. These VM instances are charged the same regardless how many apps are running on them. To avoid unexpected charges, see [Clean up an App Service plan](app-service-plan-manage.md#delete).
79
-
- In the **Isolated** tier, the App Service Environment defines the number of isolated workers that run your apps, and _each worker_ is charged hourly. In addition, there's an hourly base fee for the running the App Service Environment itself.
80
-
- (Azure Functions only) The **Consumption** tier dynamically allocates VM instances to service a function app's workload, and is charged dynamically per second by Azure. For more information, see [Azure Functions pricing](https://azure.microsoft.com/pricing/details/functions/).
77
+
- In the dedicated compute tiers (**Basic**, **Standard**, **Premium**, **PremiumV2**), the App Service plan defines the number of VM instances the apps are scaled to, so _each VM instance_ in the App Service plan has an hourly charge. These VM instances are charged the same regardless how many apps are running on them. To avoid unexpected charges, see [Clean up an App Service plan](app-service-plan-manage.md#delete).
78
+
- In the **Isolated** tier, the App Service Environment defines the number of isolated workers that run your apps, and _each worker_ is charged hourly. In addition, there's an hourly base fee for the running the App Service Environment itself.
81
79
82
80
You don't get charged for using the App Service features that are available to you (configuring custom domains, SSL certificates, deployment slots, backups, etc.). The exceptions are:
Copy file name to clipboardExpand all lines: articles/application-gateway/rewrite-http-headers.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -99,7 +99,7 @@ To configure HTTP header rewrite, you need to complete these steps.
99
99
100
100
2. Attach the rewrite set (*rewriteRuleSet*) to a routing rule. The rewrite configuration is attached to the source listener via the routing rule. When you use a basic routing rule, the header rewrite configuration is associated with a source listener and is a global header rewrite. When you use a path-based routing rule, the header rewrite configuration is defined on the URL path map. In that case, it applies only to the specific path area of a site.
101
101
> [!NOTE]
102
-
> URL Rewrite alter the headers; it does change the URL for the path.
102
+
> URL Rewrite alter the headers; it does not change the URL for the path.
103
103
104
104
You can create multiple HTTP header rewrite sets and apply each rewrite set to multiple listeners. But you can apply only one rewrite set to a specific listener.
Copy file name to clipboardExpand all lines: articles/azure-functions/functions-run-local.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -89,7 +89,7 @@ The following steps use Homebrew to install the Core Tools on macOS.
89
89
90
90
The following steps use [APT](https://wiki.debian.org/Apt) to install Core Tools on your Ubuntu/Debian Linux distribution. For other Linux distributions, see the [Core Tools readme](https://github.com/Azure/azure-functions-core-tools/blob/master/README.md#linux).
91
91
92
-
1. Register the Microsoft product key as trusted:
92
+
1. Install the Microsoft package repository GPG key, to validate package integrity:
Windows Defender ATP installation on Windows VMs via Security Center and the associated alerts are not available.
39
39
40
-
### Alerts and notifications
41
-
42
-
-**Email notifications for high severity alerts and JIT access**
43
-
Alerts and just-in-time access will function normally. However, email notifications are not available.
40
+
### Notifications
44
41
45
42
-**Azure activity logs**
46
43
User activity in Security Center is not logged in Azure activity logs in Microsoft Azure Government. This means that there’s no trace or audit for user performed actions.
0 commit comments