Skip to content

Commit 80a148f

Browse files
authored
Update migrate-application-authentication-to-azure-active-directory.md
1 parent c97a7c9 commit 80a148f

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/active-directory/manage-apps/migrate-application-authentication-to-azure-active-directory.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -191,7 +191,7 @@ The following articles are about our customer and partner’s success stories, a
191191

192192
### Find your apps
193193

194-
The first decision point in an application migration is which apps to migrate, which if any should remain, and which apps to deprecate. There is always an opportunity to deprecate the apps that you won't use in your organization. There are several ways to find apps in your organization. While discovering apps, ensure you include in-development and planned apps. Use Azure AD for authentication in all future apps.
194+
The first decision point in an application migration is which apps to migrate, which if any should remain, and which apps to deprecate. There's always an opportunity to deprecate the apps that you won't use in your organization. There are several ways to find apps in your organization. While discovering apps, ensure you include in-development and planned apps. Use Azure AD for authentication in all future apps.
195195

196196
Discover applications using ADFS:
197197

@@ -270,8 +270,8 @@ You usually develop LoB apps for your organization’s in-house use. If you've n
270270
Apps without clear owners and clear maintenance and monitoring present a security risk for your organization. Consider deprecating applications when:
271271

272272
- Their **functionality is highly redundant** with other systems
273-
- There is **no business owner**
274-
- There is clearly **no usage**
273+
- There's **no business owner**
274+
- There's clearly **no usage**
275275

276276
We recommend that you **do not deprecate high impact, business-critical applications**. In those cases, work with business owners to determine the right strategy.
277277

@@ -311,7 +311,7 @@ You can choose to begin the app migration with either the lowest priority apps o
311311

312312
In a scenario where you may not have experience using Azure AD and Identity services, consider moving your **lowest priority apps** to Azure AD first. This minimizes your business impact, and you can build momentum. Once you've successfully moved these apps and have gained the stakeholder’s confidence, you can continue to migrate the other apps.
313313

314-
If there is no clear priority, you should consider moving the apps that are in the [Azure AD Gallery](https://azuremarketplace.microsoft.com/marketplace/apps/category/azure-active-directory-apps) first and support multiple identity providers because they are easier to integrate. It is likely that these apps are the **highest-priority apps** in your organization. To help integrate your SaaS applications with Azure AD, we have developed a collection of [tutorials](../saas-apps/tutorial-list.md) that walk you through configuration.
314+
If there's no clear priority, you should consider moving the apps that are in the [Azure AD Gallery](https://azuremarketplace.microsoft.com/marketplace/apps/category/azure-active-directory-apps) first and support multiple identity providers because they are easier to integrate. It is likely that these apps are the **highest-priority apps** in your organization. To help integrate your SaaS applications with Azure AD, we have developed a collection of [tutorials](../saas-apps/tutorial-list.md) that walk you through configuration.
315315

316316
When you've a deadline to migrate the apps, these highest priority apps bucket takes the major workload. You can eventually select the lower priority apps as they won't change the cost even though you've moved the deadline.
317317

0 commit comments

Comments
 (0)