Skip to content

Commit 6bd1db2

Browse files
authored
Merge pull request #213039 from MicrosoftDocs/main
Out of Band Publishing
2 parents 0260af1 + ec90ebc commit 6bd1db2

File tree

178 files changed

+1614
-1058
lines changed

Some content is hidden

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

178 files changed

+1614
-1058
lines changed

.openpublishing.redirection.azure-monitor.json

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5441,5 +5441,11 @@
54415441
"redirect_url": "/azure/azure-sql/database/sql-insights-troubleshoot",
54425442
"redirect_document_id": false
54435443
}
5444+
,
5445+
{
5446+
"source_path_from_root": "/articles/azure-monitor/autoscale/autoscale-virtual-machine-scale-sets.md",
5447+
"redirect_url": "/azure/virtual-machine-scale-sets/tutorial-autoscale-template",
5448+
"redirect_document_id": false
5449+
}
54445450
]
54455451
}

.openpublishing.redirection.json

Lines changed: 37 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,10 @@
11
{
22
"redirections": [
3+
{
4+
"source_path": "articles/site-recovery/deploy-vmware-azure-replication-appliance-preview.md",
5+
"redirect_url": "/azure/site-recovery/deploy-vmware-azure-replication-appliance-modernized",
6+
"redirect_document_id": false
7+
},
38
{
49
"source_path": "articles/iot-hub/iot-hub-rm-template.md",
510
"redirect_url": "/azure/iot-hub/iot-hub-rm-template-powershell",
@@ -11,14 +16,39 @@
1116
"redirect_document_id": false
1217
},
1318
{
14-
"source_path": "articles/visual-studio/vs-storage-cloud-services-getting-started-queues.md",
15-
"redirect_url": "/previous-versions/azure/visual-studio/vs-storage-cloud-services-getting-started-queues",
16-
"redirect_document_id": false
19+
"source_path": "articles/site-recovery/failover-failback-overview-preview.md",
20+
"redirect_url": "/azure/site-recovery/failover-failback-overview-modernized",
21+
"redirect_document_id": false
1722
},
1823
{
19-
"source_path": "articles/visual-studio/vs-storage-cloud-services-getting-started-tables.md",
20-
"redirect_url": "/previous-versions/azure/visual-studio/vs-storage-cloud-services-getting-started-tables",
21-
"redirect_document_id": false
24+
"source_path": "articles/site-recovery/switch-replication-appliance-preview.md",
25+
"redirect_url": "/azure/site-recovery/switch-replication-appliance-modernized",
26+
"redirect_document_id": false
27+
},
28+
{
29+
"source_path": "articles/site-recovery/upgrade-mobility-service-preview.md",
30+
"redirect_url": "/azure/site-recovery/upgrade-mobility-service-modernized",
31+
"redirect_document_id": false
32+
},
33+
{
34+
"source_path": "articles/site-recovery/vmware-azure-set-up-replication-tutorial-preview.md",
35+
"redirect_url": "/azure/site-recovery/vmware-azure-set-up-replication-tutorial-modernized",
36+
"redirect_document_id": false
37+
},
38+
{
39+
"source_path": "articles/site-recovery/vmware-azure-architecture-preview.md",
40+
"redirect_url": "/azure/site-recovery/vmware-azure-architecture-modernized",
41+
"redirect_document_id": false
42+
},
43+
{
44+
"source_path": "articles/physical-server-azure-architecture-preview.md",
45+
"redirect_url": "/azure/physical-server-azure-architecture-modernized",
46+
"redirect_document_id": false
47+
},
48+
{
49+
"source_path": "articles/vmware-azure-tutorial-failover-failback-preview.md",
50+
"redirect_url": "/azure/vmware-azure-tutorial-failover-failback-modernized",
51+
"redirect_document_id": false
2252
},
2353
{
2454
"source_path": "articles/automanage/automanage-virtual-machines.md",
@@ -28841,3 +28871,4 @@
2884128871
}
2884228872
]
2884328873
}
28874+

articles/active-directory/fundamentals/automate-provisioning-to-applications-introduction.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ Thousands of organizations are running Azure AD cloud-hosted services, with its
3434
| What | From | To | Read |
3535
| - | - | - | - |
3636
| Employees and contractors| HR systems| AD and Azure AD| [Connect identities with your system of record](automate-provisioning-to-applications-solutions.md) |
37-
| Existing AD users and groups| AD| Azure AD| [Synchronize identities between Azure AD and Active Directory](automate-provisioning-to-applications-solutions.md) |
37+
| Existing AD users and groups| AD DS| Azure AD| [Synchronize identities between Azure AD and Active Directory](automate-provisioning-to-applications-solutions.md) |
3838
| Users, groups| Azure AD| SaaS and on-prem apps| [Automate provisioning to non-Microsoft applications](../governance/entitlement-management-organization.md) |
3939
| Access rights| Azure AD Identity Governance| SaaS and on-prem apps| [Entitlement management](../governance/entitlement-management-overview.md) |
4040
| Existing users and groups| AD, SaaS and on-prem apps| Identity governance (so I can review them)| [Azure AD Access reviews](../governance/access-reviews-overview.md) |

articles/active-directory/fundamentals/automate-provisioning-to-applications-solutions.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ The Azure AD provisioning service enables organizations to [bring identities fro
3535

3636
### On-premises HR + joining multiple data sources
3737

38-
To create a full user profile for an employee identity, organizations often merge information from multiple HR systems, databases, and other user data stores. MIM provides a rich set of [connectors](https://learn.microsoft.com/microsoft-identity-manager/supported-management-agents) and integration solutions interoperating with heterogeneous platforms.
38+
To create a full user profile for an employee identity, organizations often merge information from multiple HR systems, databases, and other user data stores. MIM provides a rich set of [connectors](https://learn.microsoft.com/microsoft-identity-manager/supported-management-agents) and integration solutions interoperating with heterogeneous platforms both on-premises and in the cloud.
3939

4040
MIM offers [rule extension](/previous-versions/windows/desktop/forefront-2010/ms698810(v=vs.100)?redirectedfrom=MSDN) and [workflow capabilities](https://microsoft.github.io/MIMWAL/) features for advanced scenarios requiring data transformation and consolidation from multiple sources. These connectors, rule extensions, and workflow capabilities enable organizations to aggregate user data in the MIM metaverse to form a single identity for each user. The identity can be [provisioned into downstream systems](/microsoft-identity-manager/microsoft-identity-manager-2016-supported-platforms) such as AD DS.
4141

@@ -49,13 +49,13 @@ The scenarios are divided by the direction of synchronization needed, and are li
4949

5050
Use the numbered sections in the next two section to cross reference the following table.
5151

52-
**Synchronize identities from AD into Azure AD**
52+
**Synchronize identities from AD DS into Azure AD**
5353

5454
1. For users in AD that need access to Office 365 or other applications that are connected to Azure AD, Azure AD Connect cloud sync is the first solution to explore. It provides a lightweight solution to create users in Azure AD, manage password rests, and synchronize groups. Configuration and management are primarily done in the cloud, minimizing your on-premises footprint. It provides high-availability and automatic failover, ensuring password resets and synchronization continue, even if there's an issue with on-premises servers.
5555

5656
1. For complex, large-scale AD to Azure AD sync needs such as synchronizing groups over 50,000 and device sync, customers can use Azure AD Connect sync to meet their needs.
5757

58-
**Synchronize identities from Azure AD into AD**
58+
**Synchronize identities from Azure AD into AD DS**
5959

6060
As customers transition identity management to the cloud, more users and groups are created directly in Azure AD. However, they still need a presence on-premises in AD DS to access various resources.
6161

@@ -134,7 +134,7 @@ After users are provisioned into Azure AD, use Lifecycle Workflows (LCW) to auto
134134
135135
### Reconcile changes made directly in the target system
136136

137-
Organizations often need a complete audit trail of what users have access to applications containing data subject to regulation. To provide an audit trail, any access provided to a user directly must be traceable through the system of record. MIM provides the [reconciliation capabilities](/microsoft-identity-manager/mim-how-provision-users-adds) to detect changes made directly in a target system and roll back the changes. In addition to detecting changes in target applications, MIM can import identities from third party applications to Azure AD. These applications often augment the set of user records that originated in the HR system.
137+
Organizations often need a complete audit trail of what users have access to applications containing data subject to regulation. To provide an audit trail, any access provided to a user directly must be traceable through the system of record. MIM provides the reconciliation capabilities to detect changes made directly in a target system and roll back the changes. In addition to detecting changes in target applications, MIM can import identities from third party applications to Azure AD. These applications often augment the set of user records that originated in the HR system.
138138

139139
### Next steps
140140

articles/active-directory/governance/lifecycle-workflow-tasks.md

Lines changed: 20 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -19,27 +19,28 @@ Lifecycle Workflows come with many pre-configured tasks that are designed to aut
1919

2020
Lifecycle Workflow's built-in tasks each include an identifier, known as **taskDefinitionID**, and can be used to create either new workflows from scratch, or inserted into workflow templates so that they fit the needs of your organization. For more information on templates available for use with Lifecycle Workflows, see: [Lifecycle Workflow Templates](lifecycle-workflow-templates.md).
2121

22-
Lifecycle Workflows currently support the following tasks:
2322

24-
|Task |taskDefinitionID |
25-
|---------|---------|
26-
|[Send welcome email to new hire](lifecycle-workflow-tasks.md#send-welcome-email-to-new-hire) | 70b29d51-b59a-4773-9280-8841dfd3f2ea |
27-
|[Generate Temporary Access Pass and send via email to user's manager](lifecycle-workflow-tasks.md#generate-temporary-access-pass-and-send-via-email-to-users-manager) | 1b555e50-7f65-41d5-b514-5894a026d10d |
28-
|[Add user to groups](lifecycle-workflow-tasks.md#add-user-to-groups) | 22085229-5809-45e8-97fd-270d28d66910 |
29-
|[Add user to teams](lifecycle-workflow-tasks.md#add-user-to-teams) | e440ed8d-25a1-4618-84ce-091ed5be5594 |
30-
|[Enable user account](lifecycle-workflow-tasks.md#enable-user-account) | 6fc52c9d-398b-4305-9763-15f42c1676fc |
31-
|[Run a custom task extension](lifecycle-workflow-tasks.md#run-a-custom-task-extension) | 4262b724-8dba-4fad-afc3-43fcbb497a0e |
32-
|[Disable user account](lifecycle-workflow-tasks.md#disable-user-account) | 1dfdfcc7-52fa-4c2e-bf3a-e3919cc12950 |
33-
|[Remove user from selected group](lifecycle-workflow-tasks.md#remove-user-from-selected-groups) | 1953a66c-751c-45e5-8bfe-01462c70da3c |
34-
|[Remove users from all groups](lifecycle-workflow-tasks.md#remove-users-from-all-groups) | b3a31406-2a15-4c9a-b25b-a658fa5f07fc |
35-
|[Remove user from teams](lifecycle-workflow-tasks.md#remove-user-from-teams) | 06aa7acb-01af-4824-8899-b14e5ed788d6 |
36-
|[Remove user from all teams](lifecycle-workflow-tasks.md#remove-users-from-all-teams) | 81f7b200-2816-4b3b-8c5d-dc556f07b024 |
37-
|[Remove all license assignments from user](lifecycle-workflow-tasks.md#remove-all-license-assignments-from-user) | 8fa97d28-3e52-4985-b3a9-a1126f9b8b4e |
38-
|[Delete user](lifecycle-workflow-tasks.md#delete-user) | 8d18588d-9ad3-4c0f-99d0-ec215f0e3dff |
39-
|[Send email to manager before user last day](lifecycle-workflow-tasks.md#send-email-to-manager-before-user-last-day) | 52853a3e-f4e5-4eb8-bb24-1ac09a1da935 |
40-
|[Send email on users last day](lifecycle-workflow-tasks.md#send-email-on-users-last-day) | 9c0a1eaf-5bda-4392-9d9e-6e155bb57411 |
41-
|[Send offboarding email to users manager after their last day](lifecycle-workflow-tasks.md#send-offboarding-email-to-users-manager-after-their-last-day) | 6f22ddd4-b3a5-47a4-a846-0d7c201a49ce |
4223

24+
Lifecycle Workflows currently support the following tasks:
25+
26+
|Task |taskdefinitionID |Category |
27+
|---------|---------|---------|
28+
|[Send welcome email to new hire](lifecycle-workflow-tasks.md#send-welcome-email-to-new-hire) | 70b29d51-b59a-4773-9280-8841dfd3f2ea | Joiner |
29+
|[Generate Temporary Access Pass and send via email to user's manager](lifecycle-workflow-tasks.md#generate-temporary-access-pass-and-send-via-email-to-users-manager) | 1b555e50-7f65-41d5-b514-5894a026d10d | Joiner |
30+
|[Add user to groups](lifecycle-workflow-tasks.md#add-user-to-groups) | 22085229-5809-45e8-97fd-270d28d66910 | Joiner, Leaver
31+
|[Add user to teams](lifecycle-workflow-tasks.md#add-user-to-teams) | e440ed8d-25a1-4618-84ce-091ed5be5594 | Joiner, Leaver
32+
|[Enable user account](lifecycle-workflow-tasks.md#enable-user-account) | 6fc52c9d-398b-4305-9763-15f42c1676fc | Joiner, Leaver
33+
|[Run a custom task extension](lifecycle-workflow-tasks.md#run-a-custom-task-extension) | 4262b724-8dba-4fad-afc3-43fcbb497a0e | Joiner, Leaver
34+
|[Disable user account](lifecycle-workflow-tasks.md#disable-user-account) | 1dfdfcc7-52fa-4c2e-bf3a-e3919cc12950 | Leaver
35+
|[Remove user from selected group](lifecycle-workflow-tasks.md#remove-user-from-selected-groups) | 1953a66c-751c-45e5-8bfe-01462c70da3c | Leaver
36+
|[Remove users from all groups](lifecycle-workflow-tasks.md#remove-users-from-all-groups) | b3a31406-2a15-4c9a-b25b-a658fa5f07fc | Leaver
37+
|[Remove user from teams](lifecycle-workflow-tasks.md#remove-user-from-teams) | 06aa7acb-01af-4824-8899-b14e5ed788d6 | Leaver |
38+
|[Remove user from all teams](lifecycle-workflow-tasks.md#remove-users-from-all-teams) | 81f7b200-2816-4b3b-8c5d-dc556f07b024 | Leaver |
39+
|[Remove all license assignments from user](lifecycle-workflow-tasks.md#remove-all-license-assignments-from-user) | 8fa97d28-3e52-4985-b3a9-a1126f9b8b4e | Leaver
40+
|[Delete user](lifecycle-workflow-tasks.md#delete-user) | 8d18588d-9ad3-4c0f-99d0-ec215f0e3dff | Leaver |
41+
|[Send email to manager before user last day](lifecycle-workflow-tasks.md#send-email-to-manager-before-user-last-day) | 52853a3e-f4e5-4eb8-bb24-1ac09a1da935 | Leaver |
42+
|[Send email on users last day](lifecycle-workflow-tasks.md#send-email-on-users-last-day) | 9c0a1eaf-5bda-4392-9d9e-6e155bb57411 | Leaver |
43+
|[Send offboarding email to users manager after their last day](lifecycle-workflow-tasks.md#send-offboarding-email-to-users-manager-after-their-last-day) | 6f22ddd4-b3a5-47a4-a846-0d7c201a49ce | Leaver |
4344

4445
## Common task parameters (preview)
4546

articles/active-directory/governance/set-employee-leave-date-time.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -27,9 +27,6 @@ In delegated scenarios, the signed-in user needs the Global Administrator role t
2727

2828
Updating the employeeLeaveDateTime requires the User-LifeCycleInfo.ReadWrite.All application permission.
2929

30-
>[!NOTE]
31-
> The User-LifeCycleInfo.ReadWrite.All permissions is currently hidden and cannot be configured in Graph Explorer or the API permission blade of app registrations.
32-
3330
## Set employeeLeaveDateTime via PowerShell
3431
To set the employeeLeaveDateTime for a user using PowerShell enter the following information:
3532

articles/active-directory/governance/understanding-lifecycle-workflows.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -25,8 +25,8 @@ The following reference document provides an overview of a workflow created usin
2525

2626
|Parameter |Display String |Description |Admin Consent Required |
2727
|---------|---------|---------|---------|
28-
|LifecycleWorkflows.Read.All | Read all Lifecycle workflows, tasks, user states| Allows the app to list and read all workflows, tasks, user states related to lifecycle workflows on behalf of the signed-in user.| Yes
29-
|LifecycleWorkflows.ReadWrite.All | Read and write all lifecycle workflows, tasks, user states.| Allows the app to create, update, list, read and delete all workflows, tasks, user states related to lifecycle workflows on behalf of the signed-in user.| Yes
28+
|LifecycleWorkflows.Read.All | Read all lifecycle workflows and tasks.| Allows the app to list and read all workflows and tasks related to lifecycle workflows on behalf of the signed-in user.| Yes
29+
|LifecycleWorkflows.ReadWrite.All | Read and write all lifecycle workflows and tasks.| Allows the app to create, update, list, read and delete all workflows and tasks related to lifecycle workflows on behalf of the signed-in user.| Yes
3030

3131
## Parts of a workflow
3232
A workflow can be broken down in to the following three main parts.

articles/aks/limit-egress-traffic.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -248,6 +248,11 @@ The following FQDN / application rules are required for using cluster extensions
248248
| **`<region>.dp.kubernetesconfiguration.azure.us`** | **`HTTPS:443`** | This address is used to fetch configuration information from the Cluster Extensions service and report extension status to the service. |
249249
| **`mcr.microsoft.com, *.data.mcr.microsoft.com`** | **`HTTPS:443`** | This address is required to pull container images for installing cluster extension agents on AKS cluster.|
250250

251+
252+
253+
> [!NOTE]
254+
> If any addon does not explicitly stated here, that means the core requirements are covering it.
255+
251256
## Restrict egress traffic using Azure firewall
252257

253258
Azure Firewall provides an Azure Kubernetes Service (`AzureKubernetesService`) FQDN Tag to simplify this configuration.

articles/aks/update-credentials.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ To check the expiration date of your service principal, use the [az ad sp creden
3737
```azurecli
3838
SP_ID=$(az aks show --resource-group myResourceGroup --name myAKSCluster \
3939
--query servicePrincipalProfile.clientId -o tsv)
40-
az ad sp credential list --id "$SP_ID" --query "[].endDate" -o tsv
40+
az ad sp credential list --id "$SP_ID" --query "[].endDateTime" -o tsv
4141
```
4242

4343
### Reset the existing service principal credential

articles/automation/TOC.yml

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -58,6 +58,10 @@
5858
href: automation-secure-asset-encryption.md
5959
- name: Management of Azure Automation data
6060
href: automation-managing-data.md
61+
- name: High availability
62+
items:
63+
- name: Availability zones
64+
href: automation-availability-zones.md
6165
- name: How-to guides
6266
items:
6367
- name: Automation Account

0 commit comments

Comments
 (0)