Merge pull request #9005 from MicrosoftDocs/main

Publish main to live, 12/10, 11:00 AM IST
MicrosoftDocs · Dec 10, 2024 · 56d72cd · 56d72cd
2 parents a5ce39f + b051585
commit 56d72cd
Show file tree

Hide file tree

Showing 11 changed files with 917 additions and 801 deletions.
diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json
@@ -15,6 +15,11 @@
       "redirect_url": "/Viva/glint/setup/monthly-release-dates",
       "redirect_document_id": false
     },
+    {
+      "source_path": "viva/learning/workday-integration.md",
+      "redirect_url": "/viva/learning/workday-intro",
+      "redirect_document_id": true
+    },    
     {
       "source_path": "viva/learning/configure-successfactors-content-source.md",
       "redirect_url": "/viva/learning/sfsf-introduction",

diff --git a/Viva/learning/TOC.yml b/Viva/learning/TOC.yml
@@ -31,7 +31,7 @@
           href: delete-content-source.md
         - name: SAP SuccessFactors
           items:
-          - name: Overview of SAP SuccessFactors
+          - name: Overview of SAP SuccessFactors integration
             href: sfsf-introduction.md
           - name: Add SAP SuccessFactors as a content source 
             href: successfactors-integration-add-as-content-source.md
@@ -51,8 +51,18 @@
               href: sharepoint-faq.md
         - name: Workday
           items:
-            - name: Workday
-              href: workday-integration.md
+            - name: Overview of Workday integration
+              href: workday-intro.md
+            - name: Create an integration system user (ISU)
+              href: workday-create-ISU.md
+            - name: Create RaaS reports 
+              href: workday-create-raas-report.md
+            - name: Generate connection parameters
+              href: workday-generate-connection-parameters.md
+            - name: Configure Workday on Viva Learning 
+              href: workday-configure-on-vl.md
+            - name: Enable SSO in Workday  
+              href: workday-enable-sso.md
             - name: Workday FAQs
               href: workday-integration-faqs.md
         - name: Cornerstone OnDemand

diff --git a/Viva/learning/configure-lms.md b/Viva/learning/configure-lms.md
@@ -4,7 +4,7 @@ ms.author: bhaswatic
 author: bhaswatic
 manager: elizapo
 ms.reviewer: chrisarnoldmsft
-ms.date: 11/25/2024
+ms.date: 11/27/2024
 audience: admin
 ms.topic: article
 ms.service: viva-learning
@@ -35,11 +35,12 @@ Learning management systems aren't enabled by default. To enable these sources,
 |---------|---------|
 |Cornerstone OnDemand |[Configure Cornerstone OnDemand as a content source](configure-cornerstone-content-source.md)         |
 |Saba    |[Configure Saba as a content source](configure-saba-content-source.md)         |
-|SAP SuccessFactors   |[Configure SAP SuccessFactors as a content source](configure-successfactors-content-source.md)         |
+|SAP SuccessFactors   |[Configure SAP SuccessFactors as a content source](sfsf-introduction.md)         |
+|Workday | [Configure Workday as a content source](workday-intro.md)|
 
 
->[!NOTE]
->Available learning management systems are subject to change. Depending on your organization, you may have access to different learning management systems than are listed here.
+> [!NOTE]
+> Available learning management systems are subject to change. Depending on your organization, you may have access to different learning management systems than are listed here.
 
 ## Dataflow architecture
 

diff --git a/Viva/learning/workday-configure-on-vl.md b/Viva/learning/workday-configure-on-vl.md
@@ -0,0 +1,54 @@
+---
+title: Configure Workday on Viva Learning
+ms.author: bhaswatic
+author: bhaswatic
+manager: elizapo
+ms.reviewer: chrisarnoldmsft
+ms.date: 11/27/2024
+audience: admin
+ms.topic: article
+ms.service: viva-learning
+search.appverid: MET150
+ms.collection:
+  - enabler-strategic
+  - m365initiative-viva-learning
+  - highpri
+  - Tier1
+ms.localizationpriority: medium
+description: Learn how to configure Workday on the Viva Learning tab and the licensing required for the process.
+---
+# Configure Workday on Viva Learning Admin tab
+
+You need to have premium Viva Learning license to configure Workday. Global Admin or Knowledge Admin role is required to access Viva Learning Admin tab.
+
+1. Sign in to your Viva Learning app
+
+2. Navigate to Admin tab, then select Manage providers from left navigation menu. 
+
+   :::image type="content" alt-text="Screenshot of the Manage Providers tab in Viva Learning." source="../media/learning/wd-s4-1.png" lightbox="../media/learning/wd-s4-1.png":::
+
+3. Select **Add provider** and select **Workday**. Select **Next**.
+
+4. Fill in the following required configuration details for Workday:
+
+   1. Display name: This information is the name of the carousel under which Workday learning content appears for your organization in Viva Learning. If you don't enter a name, it displays the name "Workday".
+
+   1. Workday catalog RaaS report URL: Enter the report URL, which was generated while creating RaaS for catalog. This URL consists of address for API endpoint and Workday username.  
+
+   1. Client ID, Client Secret, and refresh token: These are the values you created while enabling OAuth.
+
+   1. Org ID (only If you want to enable the LRS). Manual full sync triggering is required for codev post adding/deleting any org ID. Full sync can be triggered from Manage providers.
+
+      :::image type="content" alt-text="Screenshot of the Configure Workday window with the fields for name and client info" source="../media/learning/wd-s4-3.png":::
+
+5. Select **Save** to activate Workday content in Viva Learning. It may take up to 24 hours for the content to display in the Viva Learning app.
+
+6. Once configured, Workday appears in the Configured providers list. You can track the sync status, sync time stamp and can download the sync logs.
+
+   :::image type="content" alt-text="Screenshot of the manage providers list that includes the configured Workday provider" source="../media/learning/wd-s4-4.png" lightbox="../media/learning/wd-s4-4.png":::
+
+7. If you want to enable LRS (Learner record sync) in Assignment and Completion, enable the LRS toggle.
+
+8. You can also use **Manage providers** to edit or delete the Workday configuration.
+
+9. Admins can also trigger full sync for catalog from "Full Sync" toggle in the catalog row.
diff --git a/Viva/learning/workday-create-ISU.md b/Viva/learning/workday-create-ISU.md
@@ -0,0 +1,114 @@
+---
+title: Create an integration system user (ISU) on Workday
+ms.author: bhaswatic
+author: bhaswatic
+manager: elizapo
+ms.reviewer: chrisarnoldmsft
+ms.date: 10/23/2024
+audience: admin
+ms.topic: article
+ms.service: viva-learning
+search.appverid: MET150
+ms.collection:
+  - enabler-strategic
+  - m365initiative-viva-learning
+  - highpri
+  - Tier1
+ms.localizationpriority: medium
+description: Learn how to Create an integration system user (ISU) on the Workday portal and assign required security access
+---
+
+# Create an integration system user (ISU) on Workday
+
+An integration system user (ISU) account is required for Microsoft Viva Learning to access your Workday tenant. You can create an ISU from the Workday portal. ISU also requires relevant security group access with permission to access Workday Learning Web Services and learning catalog.
+
+1. Access the **Create Integration System User** task. Workday automatically sets the value of **Session Timeout Minutes** to zero to prevent the integration system user session from expiring. Expired sessions can cause the integration to stop before it successfully completes.
+
+2. Create a username and password. Workday recommends using **ISU_Microsoft_Viva_Learning** for the username. **Note:** The username can be customized.
+
+   :::image type="content" alt-text="Screenshot of the menu of Create Integration System User with account information fields." source="../media/learning/wd-s1-1-create-integration-system-user.png" lightbox="../media/learning/wd-s1-1-create-integration-system-user.png":::
+
+3. Access the **Create Security Group** task and select **Integration System Security Group (Unconstrained)**.
+
+4. Provide a group name. Workday recommends using **ISU_Microsoft_Viva_Learning**. It doesn’t need to be the same as the ISU name. 
+
+    :::image type="content" alt-text="Screenshot of the type of tenanted security group and name fields" source="../media/learning/wd-s1-2-create-security-group.png" lightbox="../media/learning/wd-s1-2-create-security-group.png":::
+
+5. Link your group to the integration system user. This lets Workday assign the integration system user as part of the Microsoft Viva Learning security group.
+
+    :::image type="content" alt-text="Screenshot of the Edit Integration System Security Group fields. " source="../media/learning/wd-s1-3-edit-integration-system.png" lightbox="../media/learning/wd-s1-3-edit-integration-system.png":::
+
+6. You need these domains in the Integration and System functional areas: Integration Security, security Configuration. Access the **Maintain Permissions for Security Group** task to update domain security policies.
+
+   :::image type="content" alt-text="Screenshot of the Maintain Permissions window with a Source Security Group added." source="../media/learning/wd-s1-4-security-group-permissions.png" lightbox="../media/learning/wd-s1-4-security-group-permissions.png":::
+
+7. In Domain Security Policy Permission, add **Get Only** access to the following domain security policies.
+
+   | Domain security policy | Description |
+   |-----| ----- |
+   | Reports: Learning Record  | This domain provides access to reports that display data related to the learning record. This permission is required for accessing RaaS report for Assignment and completion sync. |
+   | Manage: Learning Content | This domain provides access to certain administrative tasks to manage learning content. This permission is required for accessing RaaS report for catalog sync. |
+   | Worker Data: Active and Terminated Workers | This domain provides access to reporting fields and data sources that include terminated workers. This domain policy is required for certain fields (Firstname, lastname, email address, ID) in User RaaS report.  |
+   | Worker Data: Current staffing information | Provides information on workers' current information such as status, length of service, seniority. Includes web services. This domain policy is required for certain fields (Worker is Terminated) in User RaaS report. |
+   | Workday Accounts | This domain provides access to the management of Workday Accounts. This domain policy is required for certain fields (username) in User RaaS report. |
+
+   :::image type="content" alt-text="Screenshot of the maintain permissions for security group screen." source="../media/learning/workday-maintain-permissions-security-group.png" lightbox="../media/learning/workday-maintain-permissions-security-group.png":::
+
+7. Run the **Activate Pending Security Policy Changes** task.
+
+8. **Advance security**: These are **optional** steps for advance security access on ISU.
+
+   1. **Optional**: **Set up course-segmented security on Workday portal**:
+    You can configure which learning content displays in Viva Learning by restricting the integration system user's access by using segmented security. You can segment security based on security categories or topics.
+
+      1. Access the **Create Learning Security Category** task or the **Create Learning Topic** task. Create security segments or topics to restrict access and add these to your learning content. You need the Learning Segment Setup domain in the System functional area.
+
+         Select the Inactive checkbox if you want to disable permissions for members of the security group. You can't inactivate the security group when you:
+
+         - Grant the security group permission to the Security Configuration domain.
+         - Include the security group as a member of another security group.
+         - Specify the security group as an administrator for another security group.
+
+      1. From the **Security Groups** prompt, select security groups to identify who has permission to access the securable content.
+
+      1. From the **Access to Segments** prompt, select security segments that you want members of the specified security groups to be able to access. Workday-owned security groups include:
+
+         - Job Application - Contingent Worker
+         - Job Application – Employee
+         - Job Application – External
+
+      1. You can't combine different types of security segments in a segment-based security group.
+
+         **Example scenario:** You want a Benefits Administrator to be able to manage only benefits-related documents. You don't want them to be able to manage payroll-related documents. Workday secures access to manage all worker documents to the Worker Data: Add Worker Documents and Worker Data: Edit and Delete Worker Documents domains.
+
+         You can create **Document Categories** - Benefits segment to identify benefits-related documents. You can then use the security segment to create a segment-based security group so Benefits Administrators can access only the benefits-related documents. 
+
+      1. Next steps:  Users with access to a domain through both a segment-based and a non-segment-based security group have permission to access all segments. Make sure you associate non-segment-based security groups with users who have permission to access all segments by:
+
+         - Reviewing all security groups on the policy before adding segment-based security groups. 
+         - Reviewing the included security groups in an aggregation security group.
+
+	  1. To provide security permissions: 
+
+         - Add the security group to security policies. 
+         - Activate pending security policy changes. 
+         - Activate the security group when you want to enable the permissions on an inactive security group. 
+
+
+    2. **Optional:** Edit domain security policies on Workday portal. You can configure which security groups have permission to access the secured items in a domain. You need the Security Configuration domain in the System functional area.
+
+        1. Access the **Domain Security Policies for Functional Area** report.
+        2. Select a security policy.
+        3. Select **Edit Permissions**.
+        4. Select the **View** or **Modify** checkbox to grant the security groups access to the report or task securable items.
+        5. Select the **Get** or **Put** checkbox to grant the security groups access to integration and report or task securable actions.
+
+    3. Activate pending security policy changes on Workday portal.
+
+       Create an active timestamp using the **Activate Pending Security Policy Changes** task. Security policy changes made since the previous active timestamp take effect immediately. The active timestamp now reflects the current time, regardless of pending changes. You can run these reports to view a detailed list of the security policy changes you’re activating: Domain security policies with pending changes, Business process security policies with pending changes.
+
+       1. Access the **Activate Pending Security Policy Changes** task.
+       1. Describe your changes in the **Comment** field.
+       1. Check the **Confirm** checkbox to activate your changes.
+       1. You can use the **View All Security Timestamps** report to roll back to a previous timestamp.
+