Skip to content

Commit 731ca82

Browse files
authored
Merge pull request #183686 from MicrosoftDocs/master
12/27/2021 PM Publish
2 parents 1e504c1 + 46020c8 commit 731ca82

File tree

50 files changed

+186
-142
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

50 files changed

+186
-142
lines changed

articles/active-directory-b2c/tutorial-create-tenant.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ You learn how to register an application in the next tutorial.
3737

3838
- An Azure subscription. If you don't have one, create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) before you begin.
3939

40-
- An Azure Azure account that's been assigned at least the [Contributor](../role-based-access-control/built-in-roles.md) role within the subscription or a resource group within the subscription is required.
40+
- An Azure account that's been assigned at least the [Contributor](../role-based-access-control/built-in-roles.md) role within the subscription or a resource group within the subscription is required.
4141

4242
## Create an Azure AD B2C tenant
4343

articles/active-directory/manage-apps/f5-big-ip-kerberos-easy-button.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -480,7 +480,7 @@ F5 provides a great BIG-IP specific paper to help diagnose KCD related issues, s
480480

481481
## Additional resources
482482

483-
* [BIG-IP Advanced configuration](https://techdocs.f5.com/kb/products/big-ip_apm/manuals/product/apm-authentication-single-sign-on-11-5-0/2.html)
483+
* [BIG-IP Advanced configuration](https://techdocs.f5.com/kb/en-us/products/big-ip_apm/manuals/product/apm-authentication-single-sign-on-11-5-0/2.html)
484484

485485
* [The end of passwords, go password-less](https://www.microsoft.com/security/business/identity/passwordless)
486486

articles/active-directory/managed-identities-azure-resources/services-support-managed-identities.md

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -476,15 +476,14 @@ Refer to the following list to configure access to Azure Resource Manager:
476476
| Azure Germany | `https://servicebus.azure.net` | ![Available][check] |
477477
| Azure China 21Vianet | `https://servicebus.azure.net` | ![Available][check] |
478478

479-
480-
### Azure Storage blobs and queues
479+
### Azure Storage blobs, queues, and tables
481480

482481
| Cloud | Resource ID | Status |
483482
|--------|------------|:-:|
484-
| Azure Global | `https://storage.azure.com/` <br /><br />`https://<account>.blob.core.windows.net` <br /><br />`https://<account>.queue.core.windows.net` | ![Available][check] |
485-
| Azure Government | `https://storage.azure.com/`<br /><br />`https://<account>.blob.core.usgovcloudapi.net` <br /><br />`https://<account>.queue.core.usgovcloudapi.net` | ![Available][check] |
486-
| Azure Germany | `https://storage.azure.com/`<br /><br />`https://<account>.blob.core.cloudapi.de` <br /><br />`https://<account>.queue.core.cloudapi.de` | ![Available][check] |
487-
| Azure China 21Vianet | `https://storage.azure.com/`<br /><br />`https://<account>.blob.core.chinacloudapi.cn` <br /><br />`https://<account>.queue.core.chinacloudapi.cn` | ![Available][check] |
483+
| Azure Global | `https://storage.azure.com/` <br /><br />`https://<account>.blob.core.windows.net` <br /><br />`https://<account>.queue.core.windows.net` <br /><br />`https://<account>.table.core.windows.net`| ![Available][check] |
484+
| Azure Government | `https://storage.azure.com/`<br /><br />`https://<account>.blob.core.usgovcloudapi.net` <br /><br />`https://<account>.queue.core.usgovcloudapi.net` <br /><br />`https://<account>.table.core.usgovcloudapi.net`| ![Available][check] |
485+
| Azure Germany | `https://storage.azure.com/`<br /><br />`https://<account>.blob.core.cloudapi.de` <br /><br />`https://<account>.queue.core.cloudapi.de` <br /><br />`https://<account>.table.core.cloudapi.de`| ![Available][check] |
486+
| Azure China 21Vianet | `https://storage.azure.com/`<br /><br />`https://<account>.blob.core.chinacloudapi.cn` <br /><br />`https://<account>.queue.core.chinacloudapi.cn` <br /><br />`https://<account>.table.core.chinacloudapi.cn`| ![Available][check] |
488487

489488
### Azure Analysis Services
490489

articles/active-directory/saas-apps/neogov-tutorial.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -77,8 +77,8 @@ Follow these steps to enable Azure AD SSO in the Azure portal.
7777

7878
| Environment | URL pattern |
7979
| -- | -- |
80-
| Production | `https://www.neogov.com/` |
81-
| Sandbox | `https://www.uat.neogov.net/` |
80+
| Production | `https://login.neogov.com/` |
81+
| Sandbox | `https://login.uat.neogov.net/` |
8282
| | |
8383

8484
b. In the **Reply URL** text box, type one of the following URLs:
@@ -129,11 +129,11 @@ In this section, you'll enable B.Simon to use Azure single sign-on by granting a
129129

130130
## Configure NEOGOV SSO
131131

132-
To configure single sign-on on **NEOGOV** side, you need to send the **App Federation Metadata Url** to [NEOGOV support team](mailto:[email protected]). They set this setting to have the SAML SSO connection set properly on both sides.
132+
To configure single sign-on on **NEOGOV** side, you need to send the **App Federation Metadata Url** to your NEOGOV implementation consultant or to the NEOGOV support team. They set this setting to have the SAML SSO connection set properly on both sides.
133133

134134
### Create NEOGOV test user
135135

136-
In this section, you create a user called B.Simon in NEOGOV. Work with [NEOGOV support team](mailto:[email protected]) to add the users in the NEOGOV platform. Users must be created and activated before you use single sign-on.
136+
In this section, you create a user called B.Simon in NEOGOV. Work with your NEOGOV implementation consultant or to the NEOGOV support team to add the users in the NEOGOV platform. Users must be created and activated before you use single sign-on.
137137

138138
## Test SSO
139139

articles/app-service/configure-custom-container.md

Lines changed: 9 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -196,21 +196,25 @@ This method works both for single-container apps or multi-container apps, where
196196

197197
::: zone pivot="container-windows"
198198

199-
You can use the *C:\home* directory in your app's file system to persist files across restarts and share them across instances. The `C:\home` in your app is provided to enable your custom container to access persistent storage.
199+
You can use the *C:\home* directory in your custom container file system to persist files across restarts and share them across instances. The `C:\home` directory is provided to enable your custom container to access persistent storage.
200200

201-
When persistent storage is disabled, writes to the `C:\home` directory aren't persisted. [Docker host logs and container logs](#access-diagnostic-logs) are saved in a default persistent shared storage that is not attached to the container. When persistent storage is enabled, all writes to the `C:\home` directory are persisted and can be accessed by all instances of a scaled-out app, and log are accessible at `C:\home\LogFiles`.
201+
When persistent storage is disabled, then writes to the `C:\home` directory are not persisted across app restarts or across multiple instances. When persistent storage is enabled, all writes to the `C:\home` directory are persisted and can be accessed by all instances of a scaled-out app. Additionally, any contents inside the `C:\home` directory of the container are overwritten by any existing files already present on the persistent storage when the container starts.
202+
203+
The only exception is the `C:\home\LogFiles` directory, which is used to store the container and application logs. This folder will always persist upon app restarts if [application logging is enabled](troubleshoot-diagnostic-logs.md?#enable-application-logging-windows) with the **File System** option, independently of the persistent storage being enabled or disabled. In other words, enabling or disabling the persistent storage will not affect the application logging behavior.
202204

203205
::: zone-end
204206

205207
::: zone pivot="container-linux"
206208

207-
You can use the */home* directory in your app's file system to persist files across restarts and share them across instances. The `/home` in your app is provided to enable your custom container to access persistent storage.
209+
You can use the */home* directory in your custom container file system to persist files across restarts and share them across instances. The `/home` directory is provided to enable your custom container to access persistent storage.
210+
211+
When persistent storage is disabled, then writes to the `/home` directory are not persisted across app restarts or across multiple instances. When persistent storage is enabled, all writes to the `/home` directory are persisted and can be accessed by all instances of a scaled-out app. Additionally, any contents inside the `/home` directory of the container are overwritten by any existing files already present on the persistent storage when the container starts.
208212

209-
When persistent storage is disabled, then writes to the `/home` directory aren't persisted across app restarts or across multiple instances. The only exception is the `/home/LogFiles` directory, which is used to store the Docker and container logs. When persistent storage is enabled, all writes to the `/home` directory are persisted and can be accessed by all instances of a scaled-out app.
213+
The only exception is the `/home/LogFiles` directory, which is used to store the container and application logs. This folder will always persist upon app restarts if [application logging is enabled](troubleshoot-diagnostic-logs.md#enable-application-logging-linuxcontainer) with the **File System** option, independently of the persistent storage being enabled or disabled. In other words, enabling or disabling the persistent storage will not affect the application logging behavior.
210214

211215
::: zone-end
212216

213-
By default, persistent storage is disabled and the setting is not exposed in the app settings. To enable it, set the `WEBSITES_ENABLE_APP_SERVICE_STORAGE` app setting via the [Cloud Shell](https://shell.azure.com). In Bash:
217+
By default, persistent storage is disabled on custom containers and the setting is exposed in the app settings. To enable it, set the `WEBSITES_ENABLE_APP_SERVICE_STORAGE` app setting value to `true` via the [Cloud Shell](https://shell.azure.com). In Bash:
214218

215219
```azurecli-interactive
216220
az webapp config appsettings set --resource-group <group-name> --name <app-name> --settings WEBSITES_ENABLE_APP_SERVICE_STORAGE=true

articles/applied-ai-services/immersive-reader/how-to-multiple-resources.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,14 +2,14 @@
22
title: "Integrate multiple Immersive Reader resources"
33
titleSuffix: Azure Applied AI Services
44
description: In this tutorial, you'll create a Node.js application that launches the Immersive Reader using multiple Immersive Reader resources.
5-
author: skamal
5+
author: nitinme
66
manager: nitinme
77

88
ms.service: applied-ai-services
99
ms.subservice: immersive-reader
1010
ms.topic: how-to
1111
ms.date: 01/14/2020
12-
ms.author: skamal
12+
ms.author: nitinme
1313
ms.custom: devx-track-js
1414
#Customer intent: As a developer, I want to learn more about the Immersive Reader SDK so that I can fully utilize all that the SDK has to offer.
1515
---

articles/azure-australia/azure-policy.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -91,19 +91,19 @@ Azure Blueprints extend the capability of Azure Policy by combining them with:
9191
* Azure Resource Groups
9292
* [Azure Resource Manager Templates](../azure-resource-manager/templates/syntax.md)
9393

94-
Blueprints allow for the creation of environment designs that deploy Azure resources from Resource Manager templates, configure Azure RBAC, and enforce and audit configuration by assigning Azure Policy. Blueprints form an editable and redeployable environment template. Once the Blueprint has been created, it can then be assigned to an Azure Subscription. Once assigned, all of the Azure resources defined within the Blueprint will be created and the Azure Policies applied. The deployment and configuration of resources defined in an Azure Blueprint can be monitored from the Azure Blueprint console in the Azure portal.
94+
Blueprints allow for the creation of environment designs that deploy Azure resources from Resource Manager templates, configure Azure RBAC, and enforce and audit configuration by assigning Azure Policy. Blueprints form an editable and redeployable environment template. Once the blueprint has been created, it can then be assigned to an Azure Subscription. Once assigned, all of the Azure resources defined within the blueprint will be created and the Azure Policies applied. The deployment and configuration of resources defined in an Azure blueprint can be monitored from the Azure Blueprints console in the Azure portal.
9595

9696
Azure Blueprints that have been edited must be republished in the Azure portal. Each time a Blueprint is republished, the version number of the Blueprint is incremented. The version number allows you to determine which specific version of a Blueprint has been deployed to an organisation's Azure Subscriptions. If desired, the currently assigned version of the Blueprint can be updated to the latest version.
9797

98-
Resources deployed using an Azure Blueprint can be configured with [Azure Resource Locks](../azure-resource-manager/management/lock-resources.md) at the time of deployment. Resource locks prevent resources from being accidentally modified or deleted.
98+
Resources deployed using an Azure blueprint can be configured with [Azure Resource Locks](../azure-resource-manager/management/lock-resources.md) at the time of deployment. Resource locks prevent resources from being accidentally modified or deleted.
9999

100-
Microsoft is developing Azure Blueprint templates for a range of industries and regulatory requirements. The current library of available Azure Blueprint definitions can be viewed in the Azure portal or the [Azure Security and Compliance Blueprint](https://servicetrust.microsoft.com/ViewPage/BlueprintOverview/) page in the Service Trust Portal.
100+
Microsoft is developing Azure Blueprints templates for a range of industries and regulatory requirements. The current library of available Azure Blueprints definitions can be viewed in the Azure portal or the [Azure Security and Compliance Blueprint](https://servicetrust.microsoft.com/ViewPage/BlueprintOverview/) page in the Service Trust Portal.
101101

102-
### Azure Blueprint artifacts
102+
### Azure Blueprints artifacts
103103

104104
To create an Azure Blueprint, you can start with a blank Blueprint template, or use one of the existing sample Blueprints as a starting point. You can add artifacts to the Blueprint that will be configured as part of deployment:
105105

106-
![Azure Blueprint Artifacts](media/blueprint-artifacts.png)
106+
![Azure Blueprints Artifacts](media/blueprint-artifacts.png)
107107

108108
These artifacts could include the Azure Resource Group and Resources and associated Azure Policy and Policy Initiatives to enforce the configuration required for your environment to be compliant you're your regulatory requirements, for example, the ISM controls for system hardening.
109109

@@ -120,4 +120,4 @@ This article explained how governance and security can be enforced with Azure Po
120120
* [Azure Policy Samples](../governance/policy/samples/index.md)
121121
* [Azure Policy Samples Repository](https://github.com/Azure/azure-policy)
122122
* [Azure Policy Definition Structure](../governance/policy/concepts/definition-structure.md)
123-
* [Azure Policy Effects](../governance/policy/concepts/effects.md)
123+
* [Azure Policy Effects](../governance/policy/concepts/effects.md)

articles/azure-monitor/essentials/diagnostic-settings.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ This article provides details on creating and configuring diagnostic settings to
1414

1515
[Platform metrics](./metrics-supported.md) are sent automatically to [Azure Monitor Metrics](./data-platform-metrics.md) by default and without configuration.
1616

17-
[Platform logs](./platform-logs-overview.md), including the Azure Activity log and resource logs, provide detailed diagnostic and auditing information for Azure resources and the Azure platform they depend on. The Activity Log exists on it own but can be routed to other locations. Resource logs are not collected until they are routed to a destination.
17+
[Platform logs](./platform-logs-overview.md), including the Azure Activity log and resource logs, provide detailed diagnostic and auditing information for Azure resources and the Azure platform they depend on. The Activity Log exists on its own but can be routed to other locations. Resource logs are not collected until they are routed to a destination.
1818

1919
Each Azure resource requires its own diagnostic setting, which defines the following criteria:
2020

@@ -318,4 +318,4 @@ Diagnostic settings do not support resourceIDs with non-ASCII characters (for ex
318318

319319
## Next steps
320320

321-
- [Read more about Azure platform Logs](./platform-logs-overview.md)
321+
- [Read more about Azure platform Logs](./platform-logs-overview.md)

articles/azure-resource-manager/management/resource-name-rules.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Resource naming restrictions
33
description: Shows the rules and restrictions for naming Azure resources.
44
ms.topic: conceptual
5-
ms.date: 12/20/2021
5+
ms.date: 12/27/2021
66
---
77

88
# Naming rules and restrictions for Azure resources
@@ -689,6 +689,7 @@ In the following tables, the term alphanumeric refers to:
689689
> | servers / elasticPools | server | 1-128 | Can't use:<br>`<>*%&:\/?` or control characters<br><br>Can't end with period or space. |
690690
> | servers / failoverGroups | global | 1-63 | Lowercase letters, numbers, and hyphens.<br><br>Can't start or end with hyphen. |
691691
> | servers / firewallRules | server | 1-128 | Can't use:<br>`<>*%&:;\/?` or control characters<br><br>Can't end with period. |
692+
> | servers / keys | server | | Must be in format:<br>`VaultName_KeyName_KeyVersion`. |
692693
693694
## Microsoft.Storage
694695

0 commit comments

Comments
 (0)