WGU C768
TECHNICAL COMMUNICATION
Task 3 Submission Portfolio
Peer Invitation Email, Communication
Analysis
and Panopto Presentation Link
CLOUD STORAGE MIGRATION • MICROSOFT SHAREPOINT ONLINE • PEER
TECHNICAL AUDIENCE
Prepared by: [Student Name]
Organization: Northstar Community Services (fictional)
Date: August 19, 2026
Submission note: Replace all bracketed placeholders, paste the verified WGU Panopto share link, and compare the packet with the
rubric in your active assessment portal. This model cannot itself include or verify a student’s recording.
, Submission Overview
Purpose: Invite technically knowledgeable peers to the cloud migration presentation,
analyze the audience-based writing choices in that invitation, provide the verified
Panopto link, and document all sources used in the presentation.
Scenario Continuity
This Task 3 packet continues the fictional Northstar Community Services scenario used in Tasks 1 and 2.
The proposed initiative migrates shared departmental files from two aging on-premises servers to Microsoft
SharePoint Online, with OneDrive for individual working files. The peer audience is the Infrastructure and
Service Desk Team, whose members understand identity, permissions, file migration, service continuity, and
end-user support.
Required Submission Components
Section Deliverable Completion status
Complete; personalize
A Professional peer invitation email
logistics
B1 Tone and diction analysis Complete
B2 Technical jargon analysis Complete
Student action
C Verified WGU Panopto presentation link
required
Complete; update if
D APA-style source list
sources change
Consistency Controls
•
Use the same recommendation, organization, cost figures, and implementation phases across Tasks 1, 2,
and 3.
•
Do not claim that the source servers will be retired before file integrity, access, recovery, and owner
acceptance are validated.
•
Do not describe native Microsoft 365 features as a complete substitute for every independent backup or
regulatory requirement.
•
Replace fictional incident metrics and costs with permitted, supportable scenario values when required by
the rubric.
C768 Technical Communication | Task 3 Page 2
TECHNICAL COMMUNICATION
Task 3 Submission Portfolio
Peer Invitation Email, Communication
Analysis
and Panopto Presentation Link
CLOUD STORAGE MIGRATION • MICROSOFT SHAREPOINT ONLINE • PEER
TECHNICAL AUDIENCE
Prepared by: [Student Name]
Organization: Northstar Community Services (fictional)
Date: August 19, 2026
Submission note: Replace all bracketed placeholders, paste the verified WGU Panopto share link, and compare the packet with the
rubric in your active assessment portal. This model cannot itself include or verify a student’s recording.
, Submission Overview
Purpose: Invite technically knowledgeable peers to the cloud migration presentation,
analyze the audience-based writing choices in that invitation, provide the verified
Panopto link, and document all sources used in the presentation.
Scenario Continuity
This Task 3 packet continues the fictional Northstar Community Services scenario used in Tasks 1 and 2.
The proposed initiative migrates shared departmental files from two aging on-premises servers to Microsoft
SharePoint Online, with OneDrive for individual working files. The peer audience is the Infrastructure and
Service Desk Team, whose members understand identity, permissions, file migration, service continuity, and
end-user support.
Required Submission Components
Section Deliverable Completion status
Complete; personalize
A Professional peer invitation email
logistics
B1 Tone and diction analysis Complete
B2 Technical jargon analysis Complete
Student action
C Verified WGU Panopto presentation link
required
Complete; update if
D APA-style source list
sources change
Consistency Controls
•
Use the same recommendation, organization, cost figures, and implementation phases across Tasks 1, 2,
and 3.
•
Do not claim that the source servers will be retired before file integrity, access, recovery, and owner
acceptance are validated.
•
Do not describe native Microsoft 365 features as a complete substitute for every independent backup or
regulatory requirement.
•
Replace fictional incident metrics and costs with permitted, supportable scenario values when required by
the rubric.
C768 Technical Communication | Task 3 Page 2
