📄 Microsoft Copilot Studio + Docusign MCP

Welcome, agent. Your objective is to reuse what already works: connect the Docusign MCP Demo server to your Copilot Studio agent and trigger an existing Workflow Builder workflow. Your agent gathers inputs. Workflow Builder executes the agreement process.

🔎 Objectives

In this mission, you’ll learn how to:

• Create Docusign Web Forms, document templates, and a Workflow Builder workflow
• Add the Docusign MCP Demo tool to your agent
• Invoke the Workflow Builder workflow from the agent
• Provide inputs in natural language for the workflow start step when testing the agent
• Bonus: add your first Microsoft MCP tool (Work IQ Calendar) to extend the agent with multi-MCP capabilities

❓ What is Docusign?

Docusign is an agreement execution engine.

It enables organizations to create, send, sign, and manage agreements digitally, reducing manual and paper-based work. Beyond eSignatures, Docusign is an Intelligent Agreement Management (IAM) platform that supports the full agreement lifecycle, from creation to tracking and storage.

💼 Why it matters

Agreements are business-critical, but manual handling causes delays and inconsistency. Docusign makes agreement processes faster, trackable, and scalable.

🏗️ What is Docusign Workflow Builder?

Workflow Builder is where agreements become automated workflows.

It defines how agreements move from data collection to document generation and signing, without manual coordination. You design a workflow once and run it consistently.

💡 Common use cases

• Employee onboarding
• Sales agreements
• Procurement approvals
• NDAs and compliance workflows

⚙️ What Workflow Builder does

• Structure multi-step workflows
• Collect inputs through Web Forms
• Generate agreements from templates and data
• Route documents between participants in the right order
• Connect to third-party applications and services
• Provide visibility into workflow progress

🧩 Key Workflow Builder capabilities

Identity Verification

Confirm signer identity before agreement completion.

Web Forms

Collect structured browser-based input before agreement generation. Captured data can automatically populate documents.

Document Generation

Automatically generate agreements and documents using collected data and reusable templates.

eSignature

Enable legally recognized electronic signatures in workflows.

App Center

Connect Workflow Builder to third-party apps and services.

Workflow Templates

Use pre-built templates for common scenarios to deploy standardized agreement flows quickly.

Agreement Desk

Centralize agreement preparation, review, and collaboration across teams.

🚀 How this works with your agent

A Copilot Studio agent does not replace the workflow — it triggers it. You are not rebuilding agreement logic from scratch. You are reusing a workflow already built in Docusign. The agent collects inputs in natural language, then Workflow Builder runs the agreement process end to end.

🛡️ Certified MCP spotlight: Docusign MCP Demo

The Docusign MCP Demo server is supported in Copilot Studio and is published as a certified MCP integration in Microsoft’s connector ecosystem.

Why this matters for your mission:

• Enterprise trust signal: Certified MCP servers go through Microsoft validation and review stages before broad availability.
• Security and compliance alignment: Certification includes checks for packaging quality, behavior validation, and security/compliance readiness.
• Responsible AI expectations: Certification review includes safety evaluation, but safe usage in your tenant still depends on implementation choices.

In practical terms, this means you are not connecting to an unknown endpoint. You are integrating a reviewed MCP server that can expose Docusign capabilities to your agent through natural language.

🔐 Security and governance guidance for this mission

Treat it as safe by design, not safe by default:

• Use the correct account and connector pairing:
  • Docusign developer account (also called a demo or sandbox account) with Docusign MCP Demo
  • Docusign production account with Docusign MCP
• Use OAuth and least-privilege accounts wherever possible.
• Keep a human in the loop for high-impact actions.
• Validate prompts and outputs before scaling into production scenarios.

✍️ Docusign MCP Demo connector notes

The Docusign MCP Demo connector is intended for sandbox testing. It is separate from the Docusign MCP production connector, and workflows do not automatically migrate between Demo and Production environments.

For this Special Ops lab, that is exactly what you want: a safe development space to test prompt-driven agreement workflows before a production rollout.

📚 Learn more about Docusign MCP and Microsoft MCP server certification

• Microsoft MCP server certification
• Docusign MCP Demo connector (Microsoft Learn)
• Docusign MCP overview

🧪 Docusign MCP Lab

In this Special Ops mission, you’ll work through two practical use cases:

• First, automate a complete employment agreement flow in Docusign.
• Second, optionally extend the flow with calendar follow-up using a second MCP tool.

✨ Use case scenario

Use case 1: Core hiring workflow (Labs 1.1–1.5)

As a recruiter,

I want to digitally deliver an employment agreement and employee offer letter,

so that candidates can review and complete signatures faster.

To complete this scenario:

• 1.1 Create a Docusign Web Form
• 1.2 Create document templates
• 1.3 Create a Docusign Workflow Builder workflow
• 1.4 Test the workflow
• 1.5 Build a custom agent in Microsoft Copilot Studio, connect Docusign MCP Demo, and trigger the workflow

Outcome: The agent collects inputs and triggers the Docusign Workflow Builder workflow you already built, end to end.

Use case 2: Multi-MCP extension (Lab 1.6)

Use case for Lab 1.6:

As a hiring manager,

I want to automatically schedule a prep meeting before the new employee’s start date,

so that I have dedicated calendar time to complete onboarding tasks.

🪾 Solution diagram

The agent is the control layer.

• The user interacts with the Copilot Studio agent, and the agent collects inputs and triggers a Docusign Workflow Builder workflow through MCP.
• Docusign handles the agreement process end to end, and additional tools such as Work IQ Calendar can extend the flow with supporting tasks.

One prompt. Multiple systems. Orchestrated execution.

✅ Prerequisites

Docusign

• Sign up for a free Docusign developer account if you don’t already have one:

  • Go to https://developers.docusign.com and select Create Account in the upper-right corner.

    

Microsoft

• Copilot Studio license
• Access to a Copilot Studio developer environment
• Administrator permissions to create solutions and agents
• A SharePoint site where you have permission to create a new folder in the Documents library

Two email addresses

To complete this lab, you need two different email addresses:

• An email address to use as the employee
• An email address to use as the hiring manager

🧪 1.1 Create a Docusign Web Form

Web Forms let organizations collect information through secure browser-based forms, which can automatically populate agreements and workflows with data. They help reduce manual data entry, improve accuracy, and streamline processes such as onboarding, registration, approvals, and agreement generation.

To learn more about Web Forms, expand the additional learning block below.

1. On the Docusign developer portal home page, select Templates.

   

2. In the left navigation pane, select Start. Select Web Forms, then select Create Web Form.

   

3. You are asked how you want to create the Web Form. Select Start From Scratch.

   

4. Enter a name for the Web Form. For example:

    Request for your contact information
   

   

5. The Web Form designer appears. By default, there are three pages: Welcome page, Untitled page, and Thank you page.

   On the Welcome page, update the following fields:

   Page title

    👋🏻 Hey there!
   

   Page subtitle

    As we kick-off the next stage in sending you an offer, we need some details from you.
   
    Please complete this form and shortly after you'll receive an Employment Agreement and Offer Letter.
   

   

6. Select the Untitled page and update the following fields:

   Page title

    Your name
   

   Page subtitle

    Please provide us with your name
   

   API reference name

    Step_CandidateName
   

   

7. Add fields to this page. Select the plus icon below the page title section in the middle of the designer.

   

8. Select Text Field.

   

9. The field attributes appear. Update the following attributes:

   Field name	Field description	Required field	API reference name
   First Name	Your first name	Yes	TextBox_FirstName

   

   

10. Repeat the same steps to add the remaining Text Fields. Select the plus icon and add new Text Fields with the following attributes:

    Field name	Field description	Required field	API reference name
    Middle Name	Your middle name	No	TextBox_MiddleName
    Surname	Your surname	Yes	TextBox_Surname
    Full Name	Your full name	Yes	TextBox_FullName

    After adding the Text Fields, select the plus icon in the left pane and select New Blank Page.

    

11. Update the following fields on the new page:

    Page title

     Address
    

    Page subtitle

     Please provide us with your physical address
    

    API reference name

     Step_CandidateAddress
    

    Repeat the same steps to add the remaining Text Fields. Select the plus icon and add new Text Fields with the following attributes:

    Note: The table below shows a generic address format. You can adjust it, but keep track of any changes because you will need them in a later step. To avoid issues in later steps, use the following address format.

    | Field name | Field description | Required field | API reference name | |——————|——————-|—————-|————————-| | Address Line 1 | Street Address | Yes | TextBox_AddressLine1 | | Address Line 2 | Suburb/District | Yes | TextBox_AddressLine2 | | City | City | Yes | TextBox_City | | Post Code | Post Code | Yes | TextBox_PostCode |

    

12. After adding the Text Fields, select Thank you page in the left pane.

    

13. Update the following fields on the Thank you page:

    Page title

     ✨ Thank you
    

    Page subtitle

     We've received your form. Expect an email soon with documents to sign.
    

    

14. Your Web Form configuration is complete. To view the end-user experience, select Preview.

    

15. The Web Form opens in preview mode. You can enter the required information on each page. Enter a name on the Your Name page and select Next.

    

16. Next, complete the Address page.

    

17. Enter information on the Address page and select Next.

    

18. A summary of the information entered on both pages is shown.

    

19. Scroll down and select Next.

    

20. An error appears next. This is expected because the Web Form is in preview mode. Select Create.

    

21. Now activate the Web Form. In the upper-right corner of the designer, select Activate.

    

22. A confirmation modal appears with an Access setting field. Leave it set to Public because it will be used in a workflow step later in the lab, and select Activate.

    

23. A confirmation message appears indicating that the Web Form was activated successfully. Select Go to Web Forms.

    Tip: If the Go to Web Forms button is not visible, navigate back to the Web Forms page.

    

24. The Web Form is shown with an Active status. You successfully built a Web Form 👏🏻

    

🧪 1.2 Create document templates

Document templates are reusable settings for sending agreements. They let you predefine documents, recipient roles, routing order, and messages. This helps you quickly create and send consistent agreement envelopes without starting from scratch every time.

To learn more about Document Templates, expand the additional learning block below.

In this lab exercise, you will create two document templates:

1. Employment Agreement
2. Employee Offer Letter

Download both sample files. These two document templates will be used in the next lab exercise when you create a workflow in Workflow Builder.

Let’s get started. ⤵️

1. Go to Templates, and in the left menu pane, select Document Templates. Select Create.

   

2. You can select the file to upload. Select Upload.

   

3. Select the Sample Employment Agreement file.

   

4. The Name field is automatically populated with the file name. In the Agreement Type field, select the chevron icon, scroll down to the Human Resources list, and select Offer Letter.

   Tip: Type Offer Letter to find it quickly.

   

5. Next, define the roles for the document template. In the Fields left pane, select the chevron icon next to Sender 1, then select Edit recipients to update the signer roles.

   What is a role in a template? 🤔

   A role is a placeholder in a template that represents the person who will take action on the document, such as signing or approving. Roles define who participates and what actions they take, even before you know the actual recipient.

   🐦 What roles are used for

   • Defining who participates in an agreement
   • Reusing templates across multiple envelopes
   • Preparing documents and fields before final recipients are known

   When the template is used, an actual person (name and email) is assigned to each predefined role.

   

6. Change the Signer 1 role name to:

    Hiring Manager
   

   Add a new recipient and set the role name to:

    Employee
   

   

7. Next, replace the placeholders in the document with fields. Start by switching to the Sender role.

   What is a field in a template? 🤔

   Fields are interactive elements added to a document so recipients can take action, such as signing or entering information.

   🐦 What fields are used for

   • Collecting recipient input, such as a signature or typed information
   • Assigning actions to specific recipients or roles
   • Pre-filling information in the document when the template is set up

   In summary: fields define where and how recipients interact with the document during the signing process.

   The two field types used in this lab exercise are:

   • Standard Fields: built-in field sets you can add to a document
   • Custom Fields: fields you create to capture specific data not covered by the standard options

   

8. Highlight the first placeholder, {EffectiveDate}, and select the standard Effective Date field in the left menu.

   Warning: The blue text in the sample document is used only to make it easier to identify placeholders where fields should be added. It is for learning purposes only; real production templates do not contain colored placeholder text.

   

9. When selected, the Effective Date field is added to the template.

   

10. Next, add a custom field. Highlight the {EmployeeFullName} placeholder, select the + icon in the Fields panel, then select Field.

    

11. In the field properties flyout, enter the following for Field Name:

     Employee Full Name
    

    When you enter a value in Field Name, the template designer searches for existing fields with the same name. If no results are found, an option appears to create a new custom field using the value you entered.

    Select the plus icon to create a new custom field for Employee Full Name.

    

12. Configure the remaining properties. Enter the following for Field Description:

     The full name of the employee
    

    Turn on the Required Field option.

    By default, Field type is Text. Keep it as Text.

    

13. Save the Employee Full Name custom field.

    

14. Repeat the same steps to add the remaining custom fields. Use them for the Sender role placeholders.

    Placeholder	Field name	Field description	Required field	Field Type
    {EmployeePosition}	Employee Position	Position the employee is fulfilling	Yes	Text
    {EmployeeStartDate}	Start Date	The start date of the employee	Yes	Date
    {SalaryAmount}	Salary	The salary of the employee	Yes	Text

    

15. Next, add the Employee Full Name field to the template’s 16. Signatures section. Highlight the {EmployeeFullName} placeholder and select the field in the Fields left pane.

    

16. Now switch to the Hiring Manager role to define the fields this recipient needs to complete. In the Fields left pane, select the chevron icon next to Sender and select Hiring Manager.

    

17. Highlight the {ManagerSignature} placeholder and select Signature in the Fields left pane.

    

18. The Signature field is added.

    

19. Repeat the same steps to add the remaining fields for the Hiring Manager and Employee roles.

    Tip: 🖱️ Don’t forget to switch roles

    Use the chevron icon in the Fields left pane to switch to the Employee role.

    

    Role	Placeholder	Field
    Hiring Manager	{ManagerFullNameSignature}	Name
    Hiring Manager	{ManagerSignedDateSignature}	Date Signed
    Employee	{EmployeeSignature}	Signature
    Employee	{EmployeeFullNameSignature}	Name
    Employee	{EmployeeSignedDateSignature}	Date Signed

20. After the fields for the Hiring Manager and Employee roles are added, the template looks like this.

    

21. In the upper-right corner, select Save as Draft. You are redirected to the document templates page, and a confirmation message appears in the lower-left corner. Then select the ellipsis icon (…) and select Publish.

    Tip: If you do not see the Save As Draft button and instead see Save and Publish, select Save and Publish.

    

22. A confirmation message appears in the lower-left corner indicating that the draft template was published.

    Now create the second document template using the Sample Offer Letter file.

    Select + Create new.

    

23. Repeat the previous steps to upload the Sample Offer Letter file and select Offer Letter as the Agreement Type.

    Select Continue.

    

24. Repeat the previous steps to create two roles in the document template: Hiring Manager and Employee.

    In the Fields left pane, select the chevron icon next to Sender 1, then select Edit recipients.

    Change the Signer 1 role name to:

     Hiring Manager
    

    Add a new recipient and set the role name to:

     Employee
    

    

25. Next, replace the placeholders in the document with fields. Start by switching to the Sender role. Highlight the {EmployeeFullName} placeholder and select the Employee Full Name field in the left menu. The field now appears in place of the placeholder.

    

26. Repeat the same steps for the remaining placeholders for the Sender role. Select existing fields from the left menu or create new fields.

    Placeholder	Field name	Create New Field	Field description	Required field	Field Type
    {EmployeeAddressLine1}	Employee Address Line 1	Yes	Apt or House No. and street name	Yes	Text
    {EmployeeAddressLine2}	Employee Address Line 2	Yes	Suburb	Yes	Text
    {EmployeeAddressCity}	Employee Address City	Yes	City	Yes	Text
    {Employee AddressPostCode}	Employee Address Post Code	Yes	Post code	Yes	Text
    {EmployeePosition}	Employee Position	No
    {EmployeeStartDate}	Start Date	No
    {DueDate}	Signed Due Date	Yes	Due date of signed agreement by employee	Yes	Date

    Tip: If you accidentally create a new field with the wrong field type (for example, if you create Signed Due Date as Text), you cannot change the field type. However, you can rename the field to [Don't use] Signed Due Date.

27. Next, use the same steps as before to add the fields for the Hiring Manager and Employee roles.

    Tip: 🖱️ Don’t forget to switch roles

    Use the chevron icon in the Fields left pane to switch to the Employee role.

    Role	Placeholder	Field
    Hiring Manager	{ManagerSignature}	Signature
    Hiring Manager	{ManagerFullNameSignature}	Name
    Employee	{EmployeeSignature}	Signature
    Employee	{EmployeeFullNameSignature}	Name
    Employee	{EmployeeSignedDateSignature}	Date Signed

    Your second document template configuration is now complete 👏🏻

    Select Preview in the upper-right corner to view the document template preview mode.

    

28. When you enter values in the fields, they appear in the template viewer.

    

29. Select the X icon in the upper-left corner to exit Preview mode, then select Save As Draft.

    Tip: If you do not see the Save As Draft button and instead see Save and Publish, select Save and Publish and skip the next two publishing steps.

    

30. A confirmation message appears in the lower-left corner indicating that the template was saved as Draft. Next, select the ellipsis icon (…) and select Publish.

    

31. The Sample Offer Letter document template is now published.

    

🏃🏻‍♀️‍➡️ Next, let’s create a workflow in Workflow Builder.

🧪 1.3 Create a Docusign Workflow Builder workflow

A Docusign Workflow Builder workflow is a tool for automating document processing, signing, and data collection. Once a workflow is configured, Workflow Builder automatically handles complex agreement processes such as notifying participants, collecting signatures, and routing data.

1. In the Docusign developer portal, select Agreements from the left menu. Select Workflows. Then select Create Workflow.

   

2. Select + Blank Workflow.

   

3. Select the ellipsis icon (…) > Rename.

   

4. Enter a workflow name and select Save. For example:

    Docusign MCP Demo
   

   

5. Select Add workflow start.

   

6. Select From an API Call and select Apply.

   

7. Select Next.

   

8. The next step is to configure workflow variables. Variables are used to store data and pass it between workflow steps. Select + Add variable and create a variable of type Text. Name it:

    Employee Full Name
   

   Select Add Variable.

   

9. Repeat the same steps for the remaining variables of type Text:

    Employee Email
   

    Hiring Manager Full Name
   

    Hiring Manager Email
   

    Employee Position
   

    Start Date
   

    Effective Date
   

    Salary
   

   

10. Select Next.

    

11. Select Automated process and select Apply.

    

12. Select Add a step.

    

13. Select Set Up Invite.

    

14. Select Configure.

    

15. Select Add Participant.

    

16. Enter the following and select Add:

     Employee
    

    

17. The Employee Name and Employee Email fields appear.

    

18. Select the Employee Full Name variable.

    

19. Select the Employee Email variable.

    

20. Select Apply.

    

21. Select Add a step.

    

22. Select Collect Data with Web Forms.

    

23. Select Configure.

    

24. Select the Request for your contact information Web Form you created earlier.

    

25. Select Next.

    

26. Select the Employee participant.

    

27. Select Continue to map data fields.

    

28. Select the Employee Full Name variable.

    

29. Select Apply.

    

30. Select Add a step.

    

31. Select Prepare a Document Template.

    

32. Select Configure.

    

33. Update Step Name:

     Employment Agreement
    

    Select the Sample Employment Agreement document template.

    

34. Select Next.

    

35. Next, configure the field values. Select Next to accept the fields that were populated automatically.

    

36. Select the Effective Date variable.

    

37. Repeat the same steps to map the remaining fields to variables. Select Next.

    

38. Use variables in the Title field. Select the Employee Full Name variable to add it.

    

39. Select the + icon next to the Effective Date variable.

    

40. Add a separator and update the format. Select Next.

    

41. Select Apply.

    

42. Select Add a step.

    

43. Select Prepare a Document Template.

    

44. Update Step Name:

     Offer Letter
    

    Select the Sample Offer Letter document template. Repeat the same steps to configure the fields for the Offer Letter template and select Apply.

    

45. Confirm the named document configuration.

    

46. Select Add a step.

    

47. Select Send Documents for Signature.

    

48. Select Configure.

    

49. Select the Employment Agreement document.

    

50. Select Add Document.

    

51. Select the Offer Letter document.

    

52. Select Next.

    

53. Select Next. (It will be sent automatically.)

    

54. Enable Set a signing order.

    

55. Set Hiring Manager to 2.

    

56. Set Employee to 1.

    

57. Select the Employee variable.

    

58. The Employee participant fields are mapped.

    

59. Select Add Participant.

    

60. Enter the following and select Add:

     Hiring Manager
    

    

61. Select the Hiring Manager Full Name variable.

    

62. Select the Hiring Manager Email variable and select Next.

    

63. For the signing session, keep the default selection: Use a direct signing session. Select Next.

    

64. Finally, configure the message the Hiring Manager will see.

    Message title:

     Complete with Docusign: Employment Agreement and Offer Letter
    

    Message:

     Please review and sign the Employment Agreement and Offer Letter.
    

    Select Next.

    

65. Select Apply to complete the workflow step configuration.

    

66. Select Add a step. Next, add a Confirmation Screen that appears to the Employee participant after signing is complete.

    

67. Select Show a Confirmation Screen.

    

68. Select Configure.

    

69. Select Employee.

    

70. Select Apply.

    

71. Select App Center.

    

72. Select SharePoint.

    

73. Select Install App.

    

74. Select Install and Authorize.

    

75. Select Connect Account.

    

76. Select Private, then select Next.

    

77. Enter a name and select Log In.

    

78. Enter credentials and select Accept.

    

79. Select the X icon to exit App Center.

    

80. Select Add a step.

    

81. Select Store files in SharePoint.

    

82. Select Configure.

    

83. Select Combined Envelope File.

    

84. Select the connection.

    

85. Select the SharePoint site.

    

86. Select the Documents drive.

    

87. Select the folder.

    

88. Select Next.

    

89. In the file name field, select the Envelope ID variable.

    

90. Select Add Text.

    

91. Enter a separator and select Add:

     _
    

    

92. Select Add Variable and select the Full Name variable.

    

93. Select Apply.

    

94. Select Save Draft.

    

95. Select Review & Publish.

    

96. Select Next.

    

97. Select the + icon next to the variable.

    

98. Select the Instance ID variable.

    

99. Select the Start Date and Time variable.

    

100. Enter a separator and select Done:

      _
     

     

101. Select Publish.

     

102. Select Authorize My Account.

     

103. Select Allow Access.

     

104. Select Publish.

     

105. Select Go to Workflows.

     

106. The workflow is shown with a Published status. You successfully built the workflow 👏🏻

     

🧪 1.4 Test the workflow

Before building the agent in Microsoft Copilot Studio, it is a good practice to test the workflow by running it. You can start a new instance and run the workflow manually.

1. Open the workflow and select Start Instance in the upper-right corner.

   

2. A modal appears where you enter values for the workflow start step variables. Fill the fields with sample data.

   Note: Use two different email addresses that you can access for Employee and Hiring Manager.

   

3. After entering the variable values, select Start.

   

4. A confirmation message appears indicating that the workflow instance has started.

   

5. Go to the inbox for the Employee participant email address and open the Docusign email. The subject is ***Test Email*** Review and complete workflow. Select Review.

   Warning: If the email is not visible in the main inbox, check the spam folder.

   

6. The first page of the Web Form loads. Select Start.

   

7. The Your Name page of the Web Form appears. Enter the Employee name you used in the workflow start sample data.

   

8. Enter sample address information on the Address page of the Web Form.

   

9. The final step in the Web Form is to review the information you entered. Select Next.

   

10. After the Web Form is submitted, the next workflow steps run automatically: using the form data to generate the employment agreement and offer letter, then requesting the Employee participant’s signature.

    Select the terms agreement checkbox and select Continue.

    

11. The employment agreement appears. The blue text shows values entered from the workflow start variables and the Web Form. Review the agreement, then select Start to sign it.

    

12. Select the Sign icon to sign the employment agreement.

    

13. A modal appears to confirm signature details and style. Keep the default style and select Adopt and Sign.

    

14. Next, review the Offer Letter. Notice that the address information now appears. Select the Sign tab icon, then select the Sign icon on the Offer Letter.

    

15. Select Adopt and Sign for the Offer Letter, then select Finish.

    

16. The Confirmation Screen you configured earlier appears.

    

17. Next, go to the inbox for the Hiring Manager participant email address and open the Docusign email. The subject is Complete with Docusign: Employment Agreement and Offer Letter. Select Review Documents.

    Warning: If the email is not visible in the main inbox, check the spam folder.

18. Sign the employment agreement and Offer Letter, then select Finish.

    

19. If you are using the same email address as your Docusign developer account, the following modal may appear. Select No Thanks.

    

20. Confirmation appears that the documents were signed successfully.

    

21. Go to the inbox for your Docusign developer account email address to find the signed agreements email.

    

22. The last step of the workflow was to upload the signed agreements to SharePoint. Go to the SharePoint folder, and the PDF file of the signed agreements appears in the list.

    

23. Open the PDF file to review the document. You successfully completed the end-to-end manual workflow test 🎉 Next, build the agent in Microsoft Copilot Studio.

    

🧪 1.5 Build a custom agent in Microsoft Copilot Studio, connect Docusign MCP Demo, and trigger the workflow

Prerequisites

• New solution: As a best practice, create a new solution before creating the agent.

• Use the new experience: This lab intentionally uses the new Copilot Studio experience. The Docusign MCP Demo tool is available there. If you switched to the classic experience for another Agent Academy lesson, turn New Experience back on before continuing.

  

Let’s get started!

1. Go to https://copilotstudio.microsoft.com and sign in with your Microsoft 365 work or school account.

   Warning: You must be in a tenant where Copilot Studio is enabled.

2. Confirm that you are in the developer environment and select Agent.

   

3. Enter the following as the agent name:

    Offer Management Agent
   

   Next, enter the agent instructions:

    You are the Offer Management Agent, an HR onboarding agent that automates offer workflows.
   
    Your goal is to streamline the process of sending, signing, and finalizing Employment Agreements and Offer Letters using Docusign Workflow Builder.
   
    ## Docusign Workflow Builder
   
    Assist users by identifying the correct workflow, collecting required inputs, and triggering document delivery to recipients.
   
    Be concise, professional, and proactive. Ask for missing information before proceeding, and confirm actions before triggering workflows.
   
    If the request cannot be fulfilled using available workflows or tools, clearly explain the limitation and suggest next steps.
   
    If the user needs to provide missing information, provide the field name from the variables of the workflow with a corresponding field description.
   
    Confirm with the user that all information is correct before triggering the workflow. If the user confirms the information is correct, trigger the workflow. If the user confirms the information is incorrect, do not trigger the workflow.
   

   Tip: These instructions define the Offer Management Agent’s role, tone, and decision flow.

   Next, add the Docusign MCP Demo tool to the agent. Under Tools in the right panel, select the plus icon.

   

4. Select the Model Context Protocol (MCP) category to filter the tool list to MCP tools. Scroll and select Docusign MCP Demo.

   

   Warning: Searching for Docusign MCP Demo or docusign in the new UI may return Docusign MCP, the production tool.

   

   Do not select Docusign MCP. Clear the search field and scroll to select Docusign MCP Demo.

5. Select Docusign MCP Server.

   

6. You need to add a new connection for your Docusign developer account. Select the chevron icon and select Create new connection.

   

7. Select Create to enter your Docusign developer account credentials.

   

8. Enter the username and password for your Docusign developer account.

   

9. The connection is created and a green check icon appears. Select Next.

   

10. A list of supported actions for the Docusign MCP Demo tool appears. Scroll to review the workflow actions. Select Confirm.

    

11. The tool is added to the agent.

    Next, change this agent’s solution in Settings. In the upper-right corner, select the ellipsis icon, then select Settings.

    

12. In the dropdown field, select the new solution you created earlier to change the agent’s solution.

    

13. Save and test the agent. Select the Preview tab, then enter and submit the following:

     Send an employment agreement and offer letter to [employee name], [email address]
    

    • Replace [employee name] with a name.
    • Replace [email address] with the Employee participant email address.

    

14. The orchestrator uses the Docusign MCP Demo tool and the instructions you added to find the workflow requirements needed to send the employment agreement and Offer Letter.

    

15. Because you provided only the Employee name and email address, the agent response asks for the remaining information required by the workflow.

    

16. Enter and submit the following text. Replace the bracketed values with real values:

     employee position is [position], effective date and start date is [MMMM d], salary is [salary dollar amount], reporting to [manager full name] [manager email address], and due signed date is [MMMM d]
    

    

17. The agent provides a summary of the variables based on the information you provided and asks you to confirm whether the information is correct. This is based on the instructions you entered when creating the agent.

    

18. Enter and submit the following text:

     Yes, information is correct.
    

    The orchestrator triggers the workflow next.

    

19. When the workflow is triggered, a confirmation and summary appear.

    

20. Follow the same steps as before to complete the workflow:

    • Go to the Employee participant email inbox, open the Docusign email, complete the Web Form, and sign the agreements.
    • Go to the Hiring Manager participant email inbox and sign the agreements.
    • Finally, the signed agreements are uploaded to SharePoint.

    Warning: If the email is not visible in the main inbox, check the spam folder.

    

    

21. You can also review the workflow instance in the Docusign developer portal, where the progress status is shown as Completed.

    

Congratulations! 🥳 You learned how to invoke a Workflow Builder workflow from an agent through the Docusign MCP Demo tool.

🧪🌟 1.6 Bonus - Add the Work IQ Calendar tool (multi-MCP capabilities)

If your tenant and user are enabled for Frontier capabilities, try the following exercise to combine a second MCP server, Work IQ Calendar, with the agent.

You will update the agent to automatically create an Outlook meeting on the calendar to review the HR onboarding pre-checklist after the Docusign Workflow Builder workflow succeeds.

Download and extract sample-skill.zip, then upload the sample-skill-outlook-pre-onboarding-checklist-meeting.zip file to the agent.

1. Update the agent instructions to include details for creating an Outlook meeting after the Workflow Builder workflow is successfully triggered. In the second paragraph of the instructions, add the following as a new line:

    When the workflow has successfully been triggered, schedule an Outlook meeting.
   

   

2. Next, add an Outlook meeting scheduling section below the Docusign Workflow Builder section.

   Tip: Agent instructions define what the agent should do and when it should do it. A skill defines how to perform a specific task reliably and consistently.

    ## Schedule Outlook meeting
    When the workflow has successfully been triggered, use the `outlook-pre-onboarding-checklist-meeting` skill to create the Outlook meeting.
   

   After updating the agent instructions, select Save.

   

3. In the right panel, under Skills, select the plus icon to upload the skill file.

   

4. Click to upload the file.

   

5. Download and extract sample-skill.zip, then upload the sample-skill-outlook-pre-onboarding-checklist-meeting.zip file to the agent.

   

6. The skill is added to the agent.

   Tip: This skill is the agent’s automation recipe for scheduling an Outlook pre-onboarding meeting after the Docusign Workflow Builder workflow succeeds.

   

7. Next, add the Work IQ Calendar (Preview) tool. Under Tools in the right panel, select the plus icon.

   

8. Select the Model Context Protocol (MCP) category to filter the tool list to MCP tools. Select the Work IQ Calendar (Preview) tool.

   

9. Create a connection for the tool using the signed-in account in your developer environment. Select the chevron icon and select Create new connection.

   

10. Select Create.

    

11. Select the signed-in account, then select Next.

    

12. A list of supported actions for the Work IQ Calendar (Preview) tool appears. Select Confirm to add the tool.

    

13. The tool is added. Select Preview and start a new test session with + New chat. Enter and submit the following text:

     Send an employment agreement and offer letter to [employee name], [email address]
    

    

14. Next, the orchestrator calls the Docusign MCP Demo tool to retrieve the workflow and workflow trigger requirements. Repeat the same steps as in the previous exercise: replace the placeholders, then submit the information to the agent.

    To verify that the instruction to create the meeting two business days earlier is followed, use an effective date and start date that fall on a Monday or Tuesday.

     employee position is [position], effective date and start date is [MMMM d], salary is [salary dollar amount], reporting to [manager full name] [manager email address], and due signed date is [MMMM d]
    

15. After you provide the information required to trigger the workflow, the orchestrator confirms that the workflow was successfully triggered, processes the skill, and calls the Work IQ Calendar (Preview) tool to create an Outlook meeting two business days before the effective date.

    

16. After the Outlook meeting is created, a summary is provided.

    First, confirmation appears that the workflow was successfully triggered.

    

17. A second confirmation provides the details of the Outlook meeting that was created.

    

18. Go to your Outlook calendar to confirm the meeting invitation. In the screenshot below, the meeting was created on Friday, two business days before the Tuesday effective date.

    

19. You can also expand the skill details in the test session to inspect the reasoning the orchestrator applied in more detail.

    

20. When you complete the workflow process, the signed documents are uploaded back to SharePoint.

✅ Mission complete

Congratulations, agent - you completed Operation Docusign MCP! You have now mastered the following skills:

✅ Workflow foundation: You built a Docusign Web Form, created reusable document templates, and configured an end-to-end Workflow Builder process.

✅ Process validation: You manually tested the workflow by running a real instance, collecting participant input, capturing signatures, and confirming document delivery.

✅ Agent integration: You built a custom Copilot Studio agent, connected the Docusign MCP Demo tool, and triggered Workflow Builder through natural language.

✅ Input-driven orchestration: You provided workflow start variables through conversational prompts and validated a successful workflow invocation.

✅ Multi-MCP extension (bonus): You added Work IQ Calendar (Preview) to combine Microsoft first-party and third-party MCP tools in one agent experience.

🏅 Claim your completion badge

Congratulations, agent - mission complete! Now it’s time to claim your badge.

Submit the badge request form and answer all required questions:

https://aka.ms/agent-academy-special-ops/docusign-mcp/form

After your submission is reviewed, you will receive an email from the Global AI Community with instructions for claiming your badge.

📚 Tactical resources

🔗 Docusign for developers

🔗 Create a developer account

🔗 Build with the Docusign MCP server

🔗 Docusign MCP overview

🔗 Connect your Docusign account to Copilot Studio

📖 Microsoft MCP server certification

📖 Docusign MCP Demo connector (Microsoft Learn)