Integration of MS Teams in Advocacy

Updated 

Seamlessly integrate your Advocacy site with MS Teams through an iframe, enhancing user convenience and productivity in perfect alignment with your team's workflow.  

With the power to embed your Advocacy site directly within MS Teams using an iframe, it enables advocates to access the Advocacy platform without leaving the MS Teams environment. 

Advantages of Integrating Advocacy Site with MS Teams 

This transformative update allows advocates to utilize all the mainstream Advocacy features within MS Teams, where they spend a significant portion of their day - eliminating the need to switch back and forth between platforms.  

How to Integrate Advocacy Site with MS Teams 

Step-1: Enabling integration through the Admin Console 

Whitelisting Origins:  

  1. Log in to the admin console and go to the Overview tab. 

  2. Scroll down to the Overview section to find Whitelist Origins.

  3. Locate the Whitelisted Origin(s) for site embed option. 

  4. Enter the Advocacy and MS Teams site URLs (https://teams.cloud.microsoft)

  5. Check the box to activate whitelisting for these URLs. 

  6. Save changes and verify if applied correctly. 

Save and Publish:  

  1. After making the necessary changes, save and publish the site. Please note that it might take up to 2 hours for changes to reflect on MS Teams when adding a page. 

Step-2: Create a new advocacy app in MS teams 

Adding advocacy app:  

  1. Add app using developer portal. For reference check this documentation.

  2. Click Import app by navigating to the Apps” tab present in the top bar in developer portal. 

  3. Import the Sprinklr provided zip folder here  

  4. Your app will get added. 

    Admin would need to configure the website URL and the branding icons within the configure tab. 

 Preview the advocacy site: 

  1. Click Preview in Teams in the top right corner of the configuration screen. 

  2. Click Add and login into the Advocacy app.

Publish within your organization: 

  1. Navigate to 'Publish' and select 'Publish to org' or use the direct 'Publish' button at the top-right within the app. 

  2. Click Publish your app.

  3. Post-approval by IT admin, the app appears in Teams store under 'Built for your org' for all employees. 

Step 3: Publishing advocacy app by IT Administrator 

Publish the advocacy app for all the employees 

  1. Go to MS Teams Admin app.

  2. Publish the advocacy site. For more instructions refer to this documentation.

  3. Once published it will now be available to the employees. 

Step-4 : Providing with permissions 

Permission policies: Permission policies control what apps you want to make available to teams users in your organization. Refer documentation.

Setup policies: It controls how apps are available within Teams to the users 

  1. Go to MS Teams Admin app 

  2. Click on the subtab ‘Setup Policies’ within “Teams Apps”. 

  3. Click on “Add” to setup policy for advocacy app. 

  4. On global policy: 

    • Add the advocacy app within installed apps to let the Employees find this app already installed within their teams app. 

    • Add the advocacy app within pinned apps to let the app get pinned for everybody within the organization. 

  5. For detailed instructions refer to this document.

  6. Another separate custom policy can also be created for the advocacy app. 

       After getting published the advocacy app will look like this: 

Appendix:  

If the admin wants to configure the advocacy site on its own 

Configuring the advocacy app in the developer portal via tabs: 

Setting up Basic Information for advocacy app: 

  1. Enter "App Names" and "Description." 

  2. Under "Developer information," add your organization's name and website. 

  3. Provide links to your organization's "Privacy Policy" and "Terms of Use." 

  4. Ensure all details are accurate and comply with your organization's policies.  

Setting up Branding for advocacy app: 

  • Color Icon: Update to match your brand. 

  • Outline Icon: Change as needed for branding consistency. 

  • Accent Color: Adjust to reflect your brand's theme. 

  • Make sure the updates align with your brand's guidelines. 

Creating tabs for advocacy app in App features: 

  1. Admin can add multiple tabs in the advocacy app like “Home”, “About”, etc. 

  2.  To add a tab, click Personal app in App Features.

  3. Click “Create your first personal app tab.”

  4. Enter “Name,” “Content URL” (append “/integration/microsoftTeams” to your advocacy site's link), and “Website URL” (same as Content URL).

  5. Click “Confirm,” then “Save.” 

Ensure URLs are accurate and have the correct appended path.

Whitelisting domain names in Teams app:

  1. Admins should go to the Domain tab to add domains for whitelisting during advocacy app configuration. 

  2. The Content URL is auto added with a personal app tab creation. 

  3. Add necessary domains like *.sprinklr.com and relevant social media domains for seamless app functionality in MS Teams. 

  4. Ensure proper domain formats and adherence to MS Teams' policies. 

Adding other configurations: 

Admins can set permissions, configure SSO, and add languages for UI localization in the advocacy app as needed. 

Adding advanced configurations: for full screen mode 

  1. Navigate to the App content sub tab within the Advanced tab. 

  2. Enable loading indicator to let users know the content is loading. 

  3. Enable Full-screen mode to let the employees use the app in full screen mode.

Teams Integration 2.0 FAQs

Within the "Whitelisted Origin(s) for Site Embed" field in admin console: add 2 URLs:

Please refer the attached video to create a zip folder. Please reach out to the Product Management team if you have any doubt.

[OPEN HOURS] Advocacy - PM_PS-20231221_160427-Meeting Recording.mp4

Reach out to your Success Manager to be able to access this video.

It does not impact Teams integration in any way. 

MS Teams allows to make policies using which Teams admin can restrict the app for certain users or allow the app for certain users. This documentation provides a detailed description of it. Teams' admin will be aware of it.

In this integration, we are embedding a webpart (advocacy site) into the MS Teams app through an iframe, and we are not requesting any permissions from Teams as such. Therefore, there are no privacy/security issues or data leakage issues.