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/manage-apps/migrate-application-authentication-to-azure-active-directory.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -81,7 +81,7 @@ Economics and security benefits drive organizations to adopt Azure AD, but full
81
81
82
82
-[Automate provisioning](../app-provisioning/user-provisioning.md) of user accounts into applications.
83
83
84
-
-Leverage Azure AD Lifecycle workflows to automate onboarding or offboarding, which might have previously been done with scripts.
84
+
-Use Azure AD Lifecycle workflows to automate onboarding or offboarding, which might have previously been done with scripts.
85
85
86
86
- Create developer efficiencies and improve the end-user experience by building your applications using the Microsoft Identity Platform with the [Microsoft Authentication Library (MSAL)](../develop/msal-overview.md).
87
87
@@ -112,7 +112,7 @@ The following table includes the key roles and their contributions:
|**Project Manager**| Project coach accountable for guiding the project, including:<br /> - gain executive support<br /> - bring in stakeholders<br /> - manage schedules, documentation, and communications |
115
-
|**Identity Architect / Azure AD App Administrator**|They're responsible for the following:<br /> - design the solution in cooperation with stakeholders<br /> - document the solution design and operational procedures for handoff to the operations team<br /> - manage the pre-production and production environments |
115
+
|**Identity Architect / Azure AD App Administrator**|Responsible for the following:<br /> - design the solution in cooperation with stakeholders<br /> - document the solution design and operational procedures for handoff to the operations team<br /> - manage the pre-production and production environments |
116
116
|**On premises AD operations team**| The organization that manages the different on-premises identity sources such as AD forests, LDAP directories, HR systems etc.<br /> - perform any remediation tasks needed before synchronizing<br /> - Provide the service accounts required for synchronization<br /> - provide access to configure federation to Azure AD |
117
117
|**IT Support Manager**| A representative from the IT support organization who can provide input on the supportability of this change from a helpdesk perspective. |
118
118
|**Security Owner**| A representative from the security team that can ensure that the plan meets the security requirements of your organization. |
@@ -126,7 +126,7 @@ Effective business engagement and communication are the keys to success. It's im
126
126
127
127
Based on the communication strategy that you have chosen for the app you may want to remind users of the pending downtime. You should also verify that there are no recent changes or business impacts that would require to postpone the deployment.
128
128
129
-
In the following table you find the minimum suggested communication to keep your stakeholders informed:
129
+
In the following table, you find the minimum suggested communication to keep your stakeholders informed:
130
130
131
131
#### Plan phases and project strategy
132
132
@@ -179,7 +179,7 @@ This ensures app owners know what the app migration and testing schedule are whe
179
179
180
180
### Best practices
181
181
182
-
The following are our customer and partner’s success stories, and suggested best practices:
182
+
The following articles are about our customer and partner’s success stories, and suggested best practices:
183
183
184
184
-[Five tips to improve the migration process to Azure Active Directory](https://techcommunity.microsoft.com/t5/Azure-Active-Directory-Identity/Five-tips-to-improve-the-migration-process-to-Azure-Active/ba-p/445364) by Patriot Consulting, a member of our partner network that focuses on helping customers deploy Microsoft cloud solutions securely.
185
185
@@ -301,7 +301,7 @@ Applications with **high usage numbers** should receive a higher value than apps
301
301
302
302

303
303
304
-
Once you have determined values for business criticality and usage, you can then determine the **application lifespan**, and create a matrix of priority. See one such matrix below:
304
+
Once you have determined values for business criticality and usage, you can then determine the **application lifespan**, and create a matrix of priority. The diagram shows the matrix.
305
305
306
306

307
307
@@ -419,7 +419,7 @@ Once you have gained business buy-in, the next step is to start migrating these
419
419
420
420
### Migration tools and guidance
421
421
422
-
Use the tools and guidance below to follow the precise steps needed to migrate your applications to Azure AD:
422
+
Use the tools and guidance provided to follow the precise steps needed to migrate your applications to Azure AD:
423
423
424
424
-**General migration guidance** – Use the whitepaper, tools, email templates, and applications questionnaire in the [Azure AD apps migration toolkit](./migration-resources.md) to discover, classify, and migrate your apps.
425
425
-**SaaS applications** – See our list of [SaaS app tutorials](../saas-apps/tutorial-list.md) and the [Azure AD SSO deployment plan](plan-sso-deployment.md) to walk through the end-to-end process.
0 commit comments