Skip to content

Commit 15535e2

Browse files
authored
Merge pull request #214943 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 da05d67 + 5b3492f commit 15535e2

File tree

4 files changed

+4
-4
lines changed

4 files changed

+4
-4
lines changed

articles/active-directory/governance/what-are-lifecycle-workflows.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ ms.collection: M365-identity-device-management
1515

1616
# What are Lifecycle Workflows? (Public Preview)
1717

18-
Azure AD Lifecycle Workflows is a new Azure AD Identity Governance service that enables organizations to manage Azure AD users by automating these three basic lifecycle processes:
18+
Lifecycle Workflows is a new Identity Governance service that enables organizations to manage Azure AD users by automating these three basic lifecycle processes:
1919

2020
- Joiner - When an individual comes into scope of needing access. An example is a new employee joining a company or organization.
2121
- Mover - When an individual moves between boundaries within an organization. This movement may require more access or authorization. An example would be a user who was in marketing is now a member of the sales organization.

articles/deployment-environments/quickstart-create-access-environments.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -83,7 +83,7 @@ Run the following steps in Azure CLI to create an Environment and configure reso
8383
8484
1. Create an environment by using a *catalog-item* ('infra-as-code' template) from the list of available catalog items.
8585
```azurecli
86-
az devcenter dev environment create -g <resource-group-name> --dev-center-name <devcenter-name>
86+
az devcenter dev environment create --dev-center-name <devcenter-name>
8787
--project-name <project-name> -n <name> --environment-type <environment-type-name>
8888
--catalog-item-name <catalog-item-name> ---catalog-name <catalog-name>
8989
```

articles/devtest/offer/quickstart-individual-credit.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -74,4 +74,4 @@ For more details go to my.visualstudio.com, or follow this link: [Use Microsoft
7474
<a name="maintain-a-subscription-to-use-monthly-credits"></a>
7575
## Troubleshoot removed/expired subscriptions
7676

77-
If your Visual Studio subscription expires or is removed, all the subscription benefits, including the monthly Azure dev/test individual credit are no longer available. To learn how to continue using Azure with a monthly credit, read "[Renew an expired subscription, purchase a new on, or transfer your Azure resources](troubleshoot-expired-removed-subscription.md)".
77+
If your Visual Studio subscription expires or is removed, all the subscription benefits, including the monthly Azure dev/test individual credit are no longer available. To learn how to continue using Azure with a monthly credit, read "[Renew an expired subscription, purchase a new one, or transfer your Azure resources](troubleshoot-expired-removed-subscription.md)".

articles/site-recovery/site-recovery-retain-ip-azure-vm-failover.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ Company A has all its apps running in Azure.
2929

3030
### Before failover
3131

32-
>[!NOTE
32+
>[!NOTE]
3333
> Replication can now be done between any two Azure regions around the world. Customers are no longer limited to enabling replication within their continent.
3434
3535
Here's the architecture before failover.

0 commit comments

Comments
 (0)