Skip to content

Commit b47c52e

Browse files
authored
Merge pull request #300891 from MicrosoftDocs/repo_sync_working_branch
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)
2 parents f95068b + e97e4fb commit b47c52e

File tree

13 files changed

+14
-14
lines changed

13 files changed

+14
-14
lines changed

articles/active-directory-b2c/policy-keys-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -75,7 +75,7 @@ If an Azure AD B2C keyset has multiple keys, only one of the keys is active at a
7575
- When the current date and time is greater than a key's activation date, Azure AD B2C activates the key and stop using the prior active key.
7676
- When the current key's expiration time has elapsed and the key container contains a new key with valid *nbf (not before)* and *exp (expiration)* times, the new key becomes active automatically. New tokens are signed with the newly active key. It's possible to keep an expired key published for token validation until disabled by an admin, but this must be requested by [filing a support request](/azure/active-directory-b2c/find-help-open-support-ticket).
7777

78-
- When the current key's expiration time has elapsed and the key container *doesn't* contain a new key with valid *not before* and *expiration* times, Azure AD B2C won't be able to use the expired key. Azure AD B2C raises an error message within a dependant component of your custom policy. To avoid this issue, you can create a default key without activation and expiration dates as a safety net.
78+
- When the current key's expiration time has elapsed and the key container *doesn't* contain a new key with valid *not before* and *expiration* times, Azure AD B2C won't be able to use the expired key. Azure AD B2C raises an error message within a dependent component of your custom policy. To avoid this issue, you can create a default key without activation and expiration dates as a safety net.
7979
- The key's endpoint (JWKS URI) of the OpenId Connect well-known configuration endpoint reflects the keys configured in the Key Container, when the Key is referenced in the [JwtIssuer Technical Profile](./jwt-issuer-technical-profile.md). An application using an OIDC library will automatically fetch this metadata to ensure it uses the correct keys to validate tokens. For more information, learn how to use [Microsoft Authentication Library](../active-directory/develop/msal-b2c-overview.md), which always fetches the latest token signing keys automatically.
8080

8181
:::image type="content" source="media/policy-keys-overview/key-rollover.png" alt-text="A diagram describing the process for key rollover in Azure AD B2C." lightbox="media/policy-keys-overview/key-rollover.png":::

articles/azure-maps/creator-facility-ontology.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -87,7 +87,7 @@ For more information, see [Create a dataset using a GeoJSON package].
8787

8888
:::zone-end
8989

90-
In addition to these common fields, each feature class defines a set of properties. Each property is defined by its data type and constraints. Some feature classes have properties that are dependent on other feature classes. Dependant properties evaluate to the `ID` of another feature class.
90+
In addition to these common fields, each feature class defines a set of properties. Each property is defined by its data type and constraints. Some feature classes have properties that are dependent on other feature classes. Dependent properties evaluate to the `ID` of another feature class.
9191

9292
The remaining sections in this article define the different feature classes and their properties that make up the facility ontology in Microsoft Azure Maps Creator.
9393

articles/azure-resource-manager/management/relocation/relocation-automation.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ If your Azure Automation instance doesn't have any configuration and the instanc
1616

1717
## Prerequisites
1818

19-
- Identify all Automation dependant resources.
19+
- Identify all Automation dependent resources.
2020
- If the system-assigned managed identity isn't being used at source, you must map user-assigned managed identity at the target.
2121
- If the target Azure Automation needs to be enabled for private access, associate with Virtual Network for private endpoint.
2222
- If the source Azure Automation is enabled with a private connection, create a private link and configure the private link with Domain Name System (DNS) at target.

articles/container-apps/networking.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -287,7 +287,7 @@ In order to create private endpoints on your Azure Container App environment, pu
287287

288288
Azure networking policies are supported with the public network access flag.
289289

290-
### <a name="private-endpoint"></a>Private endpoint (preview)
290+
### <a name="private-endpoint"></a>Private endpoint
291291

292292
Azure private endpoint enables clients located in your private network to securely connect to your Azure Container Apps environment through Azure Private Link. A private link connection eliminates exposure to the public internet. Private endpoints use a private IP address in your Azure virtual network address space.
293293

articles/event-grid/custom-disaster-recovery-client-side.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ The following table illustrates the client-side failover and geo disaster recove
3737
2. Create and configure your **secondary** Event Grid resource.
3838
3. Keep in mind both resources must have the same configuration, subresources and capabilities enabled.
3939
4. Event Grid resources must be hosted in different regions.
40-
5. If the Event Grid resource has dependant resources like a storage resource for dead-lettering you should use the same region used in the secondary Event Grid resource.
40+
5. If the Event Grid resource has dependent resources like a storage resource for dead-lettering you should use the same region used in the secondary Event Grid resource.
4141
6. Ensure your endpoints are regularly tests to provide warranty your recovery plan resources are in place and functioning correctly.
4242

4343
## Basic client-side failover implementation sample for custom topics

articles/private-5g-core/deploy-private-mobile-network-with-site-powershell.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -165,7 +165,7 @@ $staticIp = New-AzMobileNetworkSimStaticIPPropertiesObject -StaticIPIpv4Address
165165
New-AzMobileNetworkSim -GroupName <SIMGROUP> -Name <SIM> -ResourceGroupName <RESOURCEGROUP> -InternationalMobileSubscriberIdentity 000000000000001 -AuthenticationKey 00112233445566778899AABBCCDDEEFF -DeviceType Mobile -IntegratedCircuitCardIdentifier 8900000000000000001 -OperatorKeyCode 00000000000000000000000000000001 -SimPolicyId "/subscriptions/<SUB_ID>/resourceGroups/<RESOURCEGROUP>/providers/Microsoft.MobileNetwork/mobileNetworks/<MOBILENETWORK>/simPolicies/<SIMPOLICY>" -StaticIPConfiguration $staticIp
166166
```
167167

168-
### Create a Site and dependant resources
168+
### Create a Site and dependent resources
169169

170170
Use `New-AzMobileNetworkSite` to create the new **Site** resource and all remaining required resources (PCCP, PCDP, and ADN). Once complete the application will be fully deployed. The example command uses the following placeholder values, replace them with the information gathered in [Prerequisite: Prepare to deploy a private mobile network and site](#prerequisite-prepare-to-deploy-a-private-mobile-network-and-site).
171171

articles/private-5g-core/whats-new.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -323,7 +323,7 @@ The 2305 release for the Azure Private 5G Core packet core is now available. For
323323

324324
**Date available:** May 31, 2023
325325

326-
New-MobileNetworkSite now supports a parameter that makes it easier to create a site and its dependant resources.
326+
New-MobileNetworkSite now supports a parameter that makes it easier to create a site and its dependent resources.
327327

328328
For details, see [Create more Packet Core instances for a site using the Azure portal](create-additional-packet-core.md).
329329

@@ -335,7 +335,7 @@ For details, see [Create more Packet Core instances for a site using the Azure p
335335

336336
It's now possible to add multiple packet cores in the same site using the Azure portal.
337337

338-
For details, see [Create a Site and dependant resources](deploy-private-mobile-network-with-site-powershell.md#create-a-site-and-dependant-resources).
338+
For details, see [Create a Site and dependent resources](deploy-private-mobile-network-with-site-powershell.md#create-a-site-and-dependent-resources).
339339

340340
## March 2023
341341

articles/role-based-access-control/permissions/migration.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -271,7 +271,7 @@ Azure service: [Azure Migrate](/azure/migrate/migrate-services-overview)
271271
> | Microsoft.Migrate/assessmentProjects/groups/sqlAssessments/write | Creates a new SQL assessment or updates an existing SQL assessment |
272272
> | Microsoft.Migrate/assessmentProjects/groups/sqlAssessments/delete | Deletes an SQL assessment |
273273
> | Microsoft.Migrate/assessmentProjects/groups/sqlAssessments/downloadurl/action | Downloads an SQL assessment report's URL |
274-
> | Microsoft.Migrate/assessmentProjects/groups/sqlAssessments/assessedSqlDatabases/read | Get the properties of assessed SQL databses |
274+
> | Microsoft.Migrate/assessmentProjects/groups/sqlAssessments/assessedSqlDatabases/read | Get the properties of assessed SQL databases |
275275
> | Microsoft.Migrate/assessmentProjects/groups/sqlAssessments/assessedSqlInstances/read | Get the properties of assessed SQL instances |
276276
> | Microsoft.Migrate/assessmentProjects/groups/sqlAssessments/assessedSqlMachines/read | Get the properties of assessed SQL machines |
277277
> | Microsoft.Migrate/assessmentProjects/groups/sqlAssessments/recommendedAssessedEntities/read | Get the properties of recommended assessed entity |

articles/service-bus-messaging/service-bus-faq.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -105,7 +105,7 @@ sections:
105105
3. Run nslookup for each one with suffixes s1, s2, and s3 to get the IP addresses of all three instances running in three availability zones,
106106
107107
> [!NOTE]
108-
> The IP address returned by the `nslookup` command isn't a static IP address. It remains constant until the underlying deployment is deleted or moved to a different cluster, however using IN addresses isn't recommended or supported, and you'll need to keep track of changes to the IP addresses.
108+
> The IP address returned by the `nslookup` command isn't a static IP address. It remains constant until the underlying deployment is deleted or moved to a different cluster, however using IP addresses isn't recommended or supported, and you'll need to keep track of changes to the IP addresses.
109109
110110
- question: |
111111
Where can I find the IP address of the client sending/receiving messages to/from a namespace?

articles/service-connector/includes/code-postgres-me-id.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -92,7 +92,7 @@ For a Spring application, if you create a connection with option `--client-type
9292

9393
Update your application following the tutorial [Bind an Azure Database for PostgreSQL to your application in Azure Spring Apps](../../spring-apps/basic-standard/how-to-bind-postgres.md#prepare-your-project). Remember to remove the `spring.datasource.password` configuration property if it was set before and add the correct dependencies to your Spring application.
9494

95-
For more tutorials, see [Use Spring Data JDBC with Azure Database for PostgreSQL](/azure/developer/java/spring-framework/configure-spring-data-jdbc-with-azure-postgresql?tabs=passwordless%2Cservice-connector&pivots=postgresql-passwordless-flexible-server#store-data-from-azure-database-for-postgresql) and [Tutorial: Deploy a Spring application to Azure Spring Apps with a passwordless connection to an Azure database](/azure/developer/java/spring-framework/deploy-passwordless-spring-database-app?tabs=postgresq).
95+
For more tutorials, see [Use Spring Data JDBC with Azure Database for PostgreSQL](/azure/developer/java/spring-framework/configure-spring-data-jdbc-with-azure-postgresql?tabs=passwordless%2Cservice-connector&pivots=postgresql-passwordless-flexible-server#store-data-from-azure-database-for-postgresql) and [Tutorial: Deploy a Spring application to Azure Spring Apps with a passwordless connection to an Azure database](/azure/developer/java/spring-framework/deploy-passwordless-spring-database-app?tabs=postgresql).
9696

9797
#### [Python](#tab/python)
9898

0 commit comments

Comments
 (0)