Skip to content

Commit 9117ac7

Browse files
authored
fix spelling, a few edits
1 parent edc09a7 commit 9117ac7

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/active-directory/saas-apps/samanage-provisioning-tutorial.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -21,16 +21,16 @@ ms.author: Zhchia
2121
# Tutorial: Configure Samanage for automatic user provisioning
2222
This tutorial describes the steps you need to perform in both Samanage and Azure Active Directory (Azure AD) to configure automatic user provisioning. When configured, Azure AD automatically provisions and de-provisions users and groups to [Samanage](https://www.samanage.com/pricing/) using the Azure AD Provisioning service. For important details on what this service does, how it works, and frequently asked questions, see [Automate user provisioning and deprovisioning to SaaS applications with Azure Active Directory](../manage-apps/user-provisioning.md).
2323

24-
## Migrating to the new Samange application
24+
## Migrate to the new Samange application
2525

26-
If you have an existing integration with Samanage, please see the below section about up coming changes. If you are setting up Samanage for the first time you can skip this section and move to **Capabilities supported**.
26+
If you have an existing integration with Samanage, please see the section below about up coming changes. If you're setting up Samanage for the first time, you can skip this section and move to **Capabilities supported**.
2727

2828
#### What's changing?
2929
* Changes on the Azure AD side: The authorization method to provision users in Samange has historically been **Basic auth**. Soon you will see the authorization method changed to **Long lived secret token**.
3030

3131

3232
#### What do I need to do to migrate my existing custom integration to the new application?
33-
If you have an existing Samanage integration with valid admin credentials, **no action is required**. We are automatically migrating customers to the new application. This is done completely behind the scenes. if the exisiting credentials expire or if you need to authorize access to the application again you will need to generate a long lived secret token. To generate a new token refer Step 2 of this article.
33+
If you have an existing Samanage integration with valid admin credentials, **no action is required**. We automatically migrate customers to the new application. This process is done completely behind the scenes. If the existing credentials expire, or if you need to authorize access to the application again, you need to generate a long-lived secret token. To generate a new token, refer to Step 2 of this article.
3434

3535

3636
#### How can I tell if my application has been migrated?

0 commit comments

Comments
 (0)