Created FY21 – Q4

Last Updated: June 22, 2021

Classified as Microsoft Confidential

 This Launch Governance Role Playbook is a living document and will grow, evolve and get updated throughout
the fiscal year. The purpose is to provide a comprehensive collection of information, specific resources and
guidance to help the PBMs to understand Launch Governance

▪ FY22 Operating Model

Topics you will ▪ E2E Operating Model Engagements

find in this ▪ Rhythm of Business to Support Operating Model
playbook ▪ Launch Assignment process
▪ PBO Governance Dashboard
▪ Partner Launch Requirement App

Personas
Partner Business Operations Key Partner Community
Stakeholder PBO Group Planning &
Manager (PBM) Account Manager Manager (PCM)
(requestor) Manager Launch (P&L) ​
(OKAM)

Classified as Microsoft Confidential

 Change History:

Slides Updated Date Changed Change Description Author

Example: Slide 6 to 8 Month/Date/Year New FY22 Operating Model Ronan Lyons, Wei Du

Classified as Microsoft Confidential

 FY22 Operating Model
Stakeholder
PBM OKAM PCM
(requestor)

Launch Requirements Gathering & Landing Change

Phase Initiate Launch Run

Intake & E2E
Stage Assessment Requirements Plan Build Deploy Transact Optimize
ODLC

Service Requester Partner Business Management (L300/400)

Monthly
Launch
Review
Meeting
/ Self -
learning

ROC VOP
Process

Launch Engagement Services

Launch Engagement
Services as needed

Commercial Partner
Community Playbook

Classified as Microsoft Confidential


1 2
Intake/ Assignment
Represent PBO
Weekly:
• P&L Partner Portfolio Review
• Review of new Launches to
determine PBM Assignment
Monthly:
• Shared Risk & Tax pipeline review
• Monthly updates to PBO on newly
assigned launches
• Monthly PBO Rolling Roadmap
Updates
More Details
Classified as Microsoft Confidential
Assigned
> PBM
• Create and maintain the Launch
OneNote tab.
• Gather Launch Requirements
• Act as the SME to provide
clarifications to PBMs/OKAM’s
• Update PBO Rolling Roadmap
• Update launch engagement services
and track KPIs
More Details
3 4
Monthly Launch
> Review Meeting
OKAM/ PBM Self
Learning
• Offline Self-learning - Launch
OneNote
Monthly Review:
PCM to update Overview of Launch
Portfolio & Roadmap
• Launch assigned PBM to update
other PBMs and OKAMs
• Highlight OKAM (1:1 engagement)
and other PBMs (RSP, 3-in-1 Area
Engagement) actions
More Details
P&L PBM OKAM PCM
Report out / Close
> the loop
• P&L Sync report out: Highlight key
issues, risks, partner impact and key
learnings to influence roadmap
• Loop Back to Launch v-team
• Share relevant requirements, issues
& risks reviewed with launch team
• Update the status of requirements
once PBM gets the status from
Launch Manager (Gather Launch
Requirements)
 1 2 3 4
Rhythm of Business to Support Operating Model

Monthly PBM/OKAM
Partner Portfolio
Tax/Shared risk Launch Review P&L Sync MBR
Review
pipeline review Meeting

Time Weekly (Commercial Monthly Monthly Monthly Monthly

Frame P&L and BP&A)

Review of key portfolio Review of Key launches 1. Visibility of key launches 1. Voice of ROC, representing Highlight key updates,
Launches to determine PBM managed by this team to 2. Validation of requirements, partner feedback on learnings and help needed
Assignment determine PBM Assignment issues & risks current launches and top across teams and leadership.
Purpose 3. Partner call to action pain point challenges.
4. Community call topics 2. Close feedback loop with
identified partners
5. Sharing of readiness
resources
PCM (Ronan) (Co-Ordinator) PBM (Mauricio)
PBO PCM (Ronan) PCM (Ronan)
PBM’s & OKAM’s OKAM (Rose)
All PBO

Audience

Classified as Microsoft Confidential

 1 2 3 4
Launch Assignment
P&L Intake
& BP&A

No
Closed loop notification
New PBO is to P&L/BP&ANo of PBM
Launch not assigned for partner
involved impacting launches

No
Partner Community

Not
YES Aligned
YES
Manager

No

YES

Assign Assign GLOBAL

REGIONAL PBM PBM with
PBM

with available available Resource

capacity capacity assignment
assessment
email sent by
PCM for group
manager
confirmation.
Feedback loop if
PBO Group
Manager

not aligned on
PCM assessment

Classified as Microsoft Confidential

 Launch Assignment 1 2 3 4

Step # Instruction (PCM)

Launch Assignment – PCM Only
1 Access One Map CRM portal

2
Search your project using Searching Box
2 (ensure filter set to all active launches if
search unsuccessful)

3 Click on “Team”

Resource Name, Ops Team i.e. (AO/IO)

Important Partner Business Operations & Role i.e.
3 Note! Partner Business Manager will already be
assigned by PCM.

PBO Governance Dashboard

Power BI here

• PBM Assigned
• PBM Awareness
• Key Launch Summary OKAM
Classified as Microsoft Confidential
 1 2 3 4
PBO Governance Dashboard
This dashboard is to be used to track PBM Launch Assignment, view launches that were assessed but not assigned and a one stop shop to view
launches that have been prioritized for discussion at our PBM ROB. It will be complimented by a Collaboration OneNote (see slide #11)

PBM Assigned: Overview of PBMs

assigned to launches that meet our
criteria

Check out the PBM

Governance dashboard here

Why is this
important?
▪ One Stop Shop for Launches Awareness Launches: Overview of the
assigned to PBM launches that have been assessed but not
Key Launch Summary: Launches flagged by PBM that feel assigned to PBMs as they don’t meet criteria or
they want to get in front of OKAMs and other PBMs. These still in pipeline
▪ Launch & Assignment Visibility will be reviewed & prioritized in Global PBM & OKAM
Monthly Review Meeting.

Classified as Microsoft Confidential

 1 2 3 4
Assigned PBM

PBM Key Activities

Launch OneNote
Create and maintain the Launch OneNote tab.
• Summary of the launch
• Latest status
• Partner Readiness Plan and Communications
• Additional internal resource for PBMs to ramp up
• Launch Engagement Services (if applicable)
• PBM 3-in-1 Area Engagement/ RSP/ OKAM Call to Actions Partner Launch
• Key Partner issues/risks Requirement App
• Maintain ‘Launch Clarifications’ tab

Gather Launch Requirements to input into Partner Launch

Requirement App
Launch Engagement
Services Request
Act as the SME to provide clarifications to PBMs/OKAM’s, capture Tool
Partner Feedback and complete post-mortem

Update Launch Engagement Services and track KPIs

PBO Rolling
Roadmap
Update PBO Rolling Roadmap

Classified as Microsoft Confidential


PBO Launch Collaboration Space
This space is a collaboration area that supports the main content in OneMap and can be used for PBO team members to share, contribute &
align on launch-specific updates. A Global PBO Launch Collaboration One Note will be used for this purpose.
Why is this
important?
▪ Somewhere to do our
homework
▪ Launch Visibility
▪ Synergy and collaboration
between the different PBO
teams are essential to our
success
▪ We’re a Partner-facing
organization and we need to
represent the partner
Check out the Global Launch
Collaboration OneNote here
Classified as Microsoft Confidential
1 2 3 4
Launch Summary: Executive overview of the launch that allows
anybody in the PBO Team to gain high level info on the launch.
Latest Status: Reflect the latest progress of the
launches here. Latest updates on the top.
Key Partner Issues/ Risks: all of
them should be captured in Partner Readiness Plan & Communications:
OneMap. But please call out any help PBMs & OKAM’s understand the
significant issues/ risks you want upcoming partner readiness activities by
to call out for specific attention. including the details like publication date,
publication channels, targeted audience, also
enclosing the links or attachments if the asset
is published. Highlight if this launch needs to
PBM 3-in-1 Area Engagement/ RSP/ be factored in for a community call or any
OKAM 1:1 engagement Call to other launch engagement services for
Actions: Provide key launch planning purposes.
information allowing other
PBMs/OKAM’s to identify key “to do” Additional Internal Resources for PBM to
items that they need to provide input ramp up: Highlight other readiness assets
on and self-serve on key information to that can be utilized by PBM’s/OKAM’s to ramp
drive relevant conversations with up on the relevant launch.
Partners/ field.
Launch Engagement Services (if applicable): For the
launches that require additional Engagement Services on
the top of the community call or fundamental calls, please
log the request and keep the status up to date as per
instruction for reporting purposes and share the execution
plan details in the dedicated tab for PBMs awareness.
 1 2 3 4
PBO Launch Collaboration Space
NEW LOOK! Launch OneNote – One Centralized location for self-serving and offline clarifications with Launch assigned PBM

Visit the Launch

OneNote here

Classified as Microsoft Confidential

 1 2 3 4
Gathering Launch Requirements
Partner Launch Requirement App gives PBMs the ability to capture and track partner
requirements for assigned launches via an easy-to-use interface.
Start capturing the Requirements in
Partner Launch Requirement App​

Update the status of requirements

PBMs are accountable for gathering partner requirements once you get the status from Launch
Manager​
for launch. Partner requirements will be gathered using:
• PBM knowledge Ensure Requirements are up to date ​
• Top + Strategic Partners (with PBMs/OKAMs)
• Community Model

All Partner requirements will be included in overall launch

Update the status of the Requirements​ on the Partner
requirements and documented in Partner Launch Launch Requirement App
Requirement App
• Requirements not accepted documented as appropriate
(e.g. logged as a risk)
Partner Launch Requirements BI
Validate requirements with PBMs/OKAMs though Launch brings to life that rich data from
Monthly Meetings and/or any offline conversations the App into amazing visuals that
tell a story for easy decision
making

Demonstrates PBMs influence to

gain launch acceptance of key
Partner requirements

Partner Launch
View SharePoint page here Requirements BI

Classified as Microsoft Confidential

 PBO Engagement Services E2E Process
Applicable services:
• Co-Design
• Pilots
• Adoption Calls
• White Glove Services
• Listening Forum
• Partner Enablement Workshop
• TQI
Why is this
important?
▪ Help partners consume and
adopt change and help them
to successfully embrace
modern experiences &
framework.
▪ Enable BI to track the resource
planning & timelines and
report out on adoption
impact KPI's
Engagement Services
Request Tool
Snackable video
Classified as Microsoft Confidential
1 2 3 4
Applicable Scenarios:
• Scenario 1 - Assigned Launch with valid OneMap ID requires additional services to land the changes and drive partners adoption -> PBO Owner:
Launch Assigned PBM to submit the request and track the KPI progress – volume = 95%
• Scenario 2: It will also cater for additional requests from other groups e.g. Trade, Finance etc. channeled through v-team (Ronan, Rui, Wei) as the front door
to PBO services (without OneMap ID) -> PBO Owner: v-team to govern and submit the request -> v-team engages PBMs for detailed planning and execution
-> Assigned PBM to follow up and close the loop – 5%
Identify Applicable Service for the request
* It is Launch Assigned PBM’s R&R to 1) keep local PBMs
engaged upfront for planning purposes – if a localized session
requires (Spanish/ JPN/ CHN/ KOR). 2) ensure localized assets
will be done through LR BOM process upfront (usually delivers 2-
week after ENG asset is available).
Submit a request (link) to obtain the
Request ID and track the progress: enter
the deployment Yr/Month | Launch Name |
PCM governs the process and Applicable Services | Assigned PBMs | Key
shares report to management Business Stakeholders | EB Event ID |
Applicable Region | Applicable Partners | KPI
team
Definition | KPI Target vs. Outcome | Request
Status
Enter your Request ID in Launch
OneNote (for Scenario 2, please refer to
Track your adoption service KPI
outcome and close the request in
tab ‘7. Additional Services request’) and
Engagement Services Request Tool
start to update your detailed Planning
and Execution information
Other PBMs/ OKAMs learn about
the planned Engagement Services
dedicated to this launch
 Key Activities – PBO Rolling Roadmap 1 2 3 4

GUIDELINES & PROCESS

Leverage Launch Governance process. PBO Rolling Roadmap updated monthly by last day of each Month.

PBM Actions
1. Assigned PBM – which will be primary contact to P&L Team/BP&A - to Open “Overview PBO Quarterly Roadmap” here
2. For launches which you are the assigned PBM, please add (new row) or update the PBO services for the month those activities are planned for
the next 4 quarters.
3. Please add launch to relevant portfolio section (Production | Commerce | co-sell | Commercial marketplace | Membership). If there are
launches that impact multiple portfolios, please copy and paste into applicable sections
a. Please use the colour coding per “PBO Key Services” tab. Note! If dates are still to be locked please add your best guestimate e.g.
content will be covered in Dec Q&A community call.
b. If more than 1 service (e.g. Q&A Community Call and Adoption Calls) please split the cell and add both PBO services.
c. Add OneNote link and OneMap (email link).
d. Check Disclaimer tab and update column “Can be shared?” with correct colour to indicate who launch can be shared with.
4. When you have completed filling out each PBO service for your assigned launch please update column “Validate launch updated f or current
month” by inputting complete. Note! Please update if no changes in adoption plan, this validation step is required.
5. If launch is complete in One Map, please update archive column to 'Yes'

PCM Action
1. PCM to add details to PPT (Internal and External view) and SP (external view) on 1 st day of each month.
2. Create archive of both excel and ppt. monthly.
3. Remove 'complete' status updates from “Overview PBO Quarterly Roadmap” here to create a clean editable version for subsequent updates

Note: Please bundle launches together that are connected where it makes sense.
Scope: High Partner Impacting Launches.
Classified as Microsoft Confidential
 PBO Rolling Roadmap Process 1 2 3 4

4th Week of each month 1st Week of each month

2
c. Identify and add OneNote link
1 Overview PBO Quarterly Roadmap b.
Identify and and OneMap Add details to PPT (Internal and
Overview PBO Quarterly PBO Rolling
validate “PBO Key External view) and Partner
Roadmap.xlsx Roadmap
Services” Use colour Launches SharePoint.
updated in a
coding per “PBO Key monthly basis
PBM to add (new row) or update the 4
Services” tab
PBO services for the month those You can identify OneMap (email link)
activities are planned for the next 4
Assigned quarters
PBM
e.
Primary
contact to Update column “Can be
P&L/BP&A shared?” and indicate who launch
Team can be shared with. Check
c.
Disclaimer tab
Create a monthly
3 5 archive of both excel
a. Update column “Validate launch and ppt.
Add launch to relevant NCE or
updated for current month” this
Production section. Recommendation: If more than 1 validation step is required.
service (e.g. Q&A Community Call Remove monthly
6
Recommendation: If there are and Adoption Calls) please split the control validation from
PCM
launches that impact multiple cell and add both PBO services. “Overview PBO Quarterly
PBM
portfolios, please copy and paste into Roadmap” here
applicable sections

Classified as Microsoft Confidential

 Monthly Launch Review Meeting 1 2 3 4
OKAM/ PBM Self Learning

Offline Self-learning - Launch OneNote

• Learn about launches to support OKAM 1:1 engagement, RSP and 3-in-1 area engagements.
• OKAM/ PBM to raise questions or provide feedback to assigned PBM for clarifications and partner close the loop.

OKAM (1:1 engagement) and other PBMs

PCM PBM Assigned (RSP, 3-in-1 Area Engagement)
Launch assigned PBM to update (follow Accountabilities:
• Overview of Launch
portfolio sequence): • E2E visibility of launch portfolios & upcoming
Portfolio;
• Launch Roadmap; launches
• Follow instructions to tag your launch in • Contribute to Partner requirements, issues & risks
• Upcoming
OneMap if you need to cover the updates ensuring the E2E Partner experience is represented
Community calls
in the meeting • Co-design plans are reviewed with input received on
agenda
• Summary of Engagement Services asks, potential partners to include & align on timelines to
timelines & Partners attend & Partner narrative
• Share & solicit info on Partner • Aware of readiness updates to consume to ramp up
requirements, key Partner issues & risks to L100
• Share readiness plans incl. upcoming • Aware of adoption asks and can discuss with their
community call topics partners & share feedback for review/consideration
• Flag key POR changes • Equipped to represent PBO in area engagement/ RSP
• Partner feedback & post-mortem input • Can close out on Voice of Partner

Classified as Microsoft Confidential

 Power BI Launch Tagging – PBM Step by Step
1 2 3 4

Launch Tagging – Launch Assigned PBM Step # Instruction (Launch Assigned PBM)
PBM are responsible of tagging their launches for discussion during the Monthly Launch
a Access One Map CRM portal
Review Meeting
Go to “Launch Summary” and then scroll-
b drown “Tags” which is visible in
b approximately middle of screen

c Select “Add” to add a new tag

PBM to type or paste “pbmreview” if you

c
d want to review that launch at monthly
PBM/OKAM review meeting
e
Save update and close (Top left corner of
e screen)

Why is this important?

PCM will use the Launch Summary Tag during the Monthly Launch Review.
The Launches flagged by PBMs will be reviewed & prioritized in Global PBM &
OKAM Monthly Review Meeting.

Classified as Microsoft Confidential

 The What: PBM Partner Business Manager & OKAM Launch Reviews 1 2 3 4

Launch assigned PBM Intake E2E Plan Build Deploy Transact OKAM / Other PBM call to
Req.
action
Launch Overview – provide overview of upcoming launches; Partner opportunity, Output: No Call to action – this is an inform
Partner impact, Partner actions & timelines for go-live

Partner Requirements – Provide overview of collated requirements to solicit further Output: Review Partner Requirements & add
input from OKAM’s to ensure requirements fully capture Partner needs & any OKAM’s additional requirements/feedback for
needs to assist adoption (Partner readiness assets for example) consideration & share prioritization
Co-Design – Provide overview of Co-Design plans including timelines, Partner asks, Output: Review Co-Design plans, share
Partner scope, Partner narrative to share & solicit OKAM’s help to determine Partners potential partners to include, align on
(if applicable) to include in scope timelines to attend & Partner narrative.
Share Partner Adoption Asks – Provide overview of Partner adoption asks so the Output: Revert with feedback on proposed
OAKM’s can review & revert with any feedback plan

Share Readiness Plans – provide OKAM’s with an advanced awareness of materials Output: Ramp up on resources to L100-150
available to consume that they can self-serve, providing additional context where in advance of Partner engagement &
needed and drive Partner engagement. Share when final assets available too. leverage resources to drive adoption &
clarity on the launch
Issues & Risks – Provide insight into top Partner issues/risks that the launch team is Output: Validate Partner experience risks &
tracking for awareness & context (where applicable), seeking validation & additional share expertise/Partner feedback for
Partner considerations consideration
Key Updates – Provide key updates that necessitate OKAM’s being informed such as Output: Inform and action where needed.
launch date shift, new scope, additional Partner asks/impacts, update on issue/risk etc.

Partner Feedback/blockers – solicit feedback from OKAM’s on how launch is landing Output: Validate Partner experience risks &
with Partners, are there blockers? Missed requirements? Add new risks/issues? Ensure share expertise/Partner feedback for
we share latest close the loop feedback to OKAM’s to share with Partners consideration. Close the loop with Partners.
Post-Mortem – solicit feedback from OKAM’s & PBM's on Partner launch (primarily Output: Share feedback to PBM to represent
focus on adoption roll out, readiness, etc) globally
Classified as Microsoft Confidential
 PBM Call to Action

Familiarise yourself with the OneNote Structure here

For launches you have been assigned to, begin filling out the
OneNote template asap. Continue to populate with latest
information as launch evolves

Determine the key launch updates to include in monthly

PBM/OKAM review meeting. Tag any launches as “pbmreview”
72 hours in advance of meeting so OKAM and other PBMs can
pre-read relevant launch information in One note

Accept invite to PBM/OKAM ROB (Monthly occurrence)

Update monthly roadmap file

Update Ad-hoc Engagement Services being planned for your

launch

Classified as Microsoft Confidential

 Office Hour Series Wrap Up
Leverage follow-up emails per session and utilize existing
material to learn.

Check FAQ document regularly to better understand the

process.

Hypercare throughout Aug 2021 via

1) local v-team contact point
• Ronan/ Wei: Launch governance;
• Melissa/ Inara: Community Framework;
• Tatiana: PBO branding, PBO Sharepoint
2) Partner Community Engagement Office Hour series will
continue.

Classified as Microsoft Confidential

Classified as Microsoft Confidential
 Launch Measures of Success
This list may be used to influence launch conditions of success, adjust per launch.
Metric Description Frequency
E2E Experience Experience progress per GTM Quarterly

Speed to Sell Days for field/partner to hit sales threshold for products post go live date Quarterly

First Pass Quality Changes returned due to issues with initial planning Quarterly

Transition to Modern Actual revenue from modern motions versus potential with current capability Monthly
PBMs are accountable

Partner co-design sessions defined and delivered in a timely manner. Attendees invited and participated Number of sessions per
Partner co-design sessions set up and delivered
actively. criteria defined
Partners were invited and attended the sessions and actively participated in the discussion. Number of
Partner participation
relevant partners attended/number of partners invited.
Requirements reviewed/consolidated by P&L. PBO on a timely manner. Number of days to review
Requirements consolidated on time
consolidated requirements

Communication on engineering decision to partners IM's and PBO to capture feedback from partners on final engineering decision and document in Design
delivered document and include mitigation plan. Feedback captured and documented

Partner readiness requirements gathered and
documented
Communication to partners on launch progress
Facilitate additional co-design session with partners
Partner Experience after launch
Adoption
Partner requirement time to market
100% ODLC Adherence to support the Microsoft
Launch Policy
Pulse Survey / Partner Sentiment Survey
Classified as Microsoft Confidential
IM's and PBO to capture feedback from partners on readiness deliverables and timelines and document in
Design document. Feedback captured and documented
Keep partners informed on requirements status and timeline. Updates on requirements not in scope, risks, Periodic launch updates
mitigation, etc. (monthly, quarterly, etc.)
Periodic review (monthly,
Keep partners in the feedback process of launch, reviewing requirements, risks and issues.
quarterly, etc.)
During warranty period or
Verbatim from partners on a positive experience with launch requirements implemented as planned.
60-90 days following
(survey)
recommended
Number of key accounts who have adopted the capability. % of top accounts who have adopted the
capability/product/service in the warranty period (90 days)
How long it took to launch and how this impacted partners. Feedback from partners surveyed.
100% adherence to all Operations Delivery Lifecycle (ODLC) requirements and the Microsoft Launch Policy
 Launch Measures of Success
Metric Description Frequency
Number of compliance risk /
issues on launches past Build
Launch Compliance
that are not accepted / with
mitigation plans
PBMs can influence

Launches where readiness

Partner readiness milestone adherence content is available by channel
SLAs (T-90 days)
Readiness asset quality -
Evaluation score of key
Asset Quality complex launch readiness
assets meet or exceed quality
expectations
Proper identification of
launches with co-design
Co-design opportunities reviewed and flagged
opportunities per criteria
defined
% of Readiness material
Readiness/Content for sessions prepared on time Content for the session prepared and delivered to partners before the calls.
delivered on time
% of requirements
Requirements reviewed and accepted by engineering P&L to review the list of requirements P0/P1/P2 with engineering and provide final decision accepted/approved by
engineering

Top partners' readiness requirements met and ready

Readiness requirements met after launch (top partners prepared for launch)
to transact

Number of months for

Amount of time that partners take to consume the capability/product/service after launch. Expected vs
Time to transaction partners to use the
Real time
capability/offer/service

Classified as Microsoft Confidential

 Examples of Process Aligned Launch Areas
Process Area Launch Areas

Billing Fees
Credit Process
Billing Invoicing Process
Revenue Recognition
Tax Related
Compliance in Order Submissions (ex Discount Transparency)
Order Overage Process
Orders (Credits & Return Policy Process
Adjustments) Order System & Tools Capability (MOET/POET)
Fulfilment (post-order)* *Technically a separate process area that we will manage under Orders
eAgreements, other contracts outside of Org Management scope
Partner Authentication (MFA, MPA)
PLM Process Optimization
Organization Management Partner M&A Processes - Offboarding
Partner Vetting Government/Compliance
Partner Segmentation
Incentives
Payouts
Discounts
New License Offer

Product Offer & Price Migration Process from Production to New Commerce (ex Charity moving from Production to CSP)

New Capability/Cloud Offers

Internal Process Optimizations
Support BPO Enhancements / Run Business
Readiness / Self-Serve Capabilities

Classified as Microsoft Confidential

 If PBM cannot attend any review meeting and
feels content cannot be self served or
represented by a colleague then can pre-cord
content and post to OneNote and this will be
played in the meeting. Please keep less than 5
mins in duration.

1. In PowerPoint, open the slide that you want

to put the screen recording on.
2. On the Insert tab of the ribbon, select Screen
Recording.
3. On the Control Dock, click Select Area, and
drag the pointer from top left to bottom right
of desired area. Click Record.
4. To control your recording:
• Click Pause to temporarily stop the recording
(Windows logo key+Shift+R).
• Click Record to resume recording (Windows
logo key+Shift+R).
• Click Stop to end your recording (Windows
logo key+Shift+Q)

5. Copy recording to this folder and copy link to

“Key to Do’s section so OKAM’s can self serve.

Classified as Microsoft Confidential

 Why is this
important?
PBM’s: See steps below in OneNote
that will allow you to view and then
edit any pre-populated questions the
OKAM’s have added.

In OneNote
• select "Recent Edits"
• on the results pane on the right,
select "Search this section" and
Sort by Author

Classified as Microsoft Confidential