Skip to content

Commit 159bd26

Browse files
authored
Merge pull request #54342 from MicrosoftDocs/NEW-surface-support-service-provider
NEW-surface-support-service-provider -> main
2 parents 5bd29f9 + bc44475 commit 159bd26

21 files changed

Lines changed: 325 additions & 0 deletions
33.3 KB
Loading

learn-pr/achievements/surface-support-service-provider-badge.svg

Lines changed: 4 additions & 0 deletions
Loading
Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
### YamlMime:ModuleUnit
2+
uid: learn.dpu.surface-support-service-provider.introduction
3+
title: Introduction
4+
metadata:
5+
title: Introduction
6+
description: This content is part of the "Managing Surface support as a service provider or partner" module.
7+
ms.date: 04/20/2026
8+
author: ozahran7
9+
ms.author: v-zahranomar
10+
ms.topic: unit
11+
durationInMinutes: 1
12+
content: |
13+
[!include[](includes/1-introduction.md)]
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
### YamlMime:ModuleUnit
2+
uid: learn.dpu.surface-support-service-provider.understand-partner-access-models-for-surface-support
3+
title: Understand partner access models for Surface support
4+
metadata:
5+
title: Understand Partner Access Models For Surface Support
6+
description: This content is part of the "Managing Surface support as a service provider or partner" module.
7+
ms.date: 04/20/2026
8+
author: ozahran7
9+
ms.author: v-zahranomar
10+
ms.topic: unit
11+
durationInMinutes: 1
12+
content: |
13+
[!include[](includes/2-understand-partner-access-models-for-surface-support.md)]
Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
### YamlMime:ModuleUnit
2+
uid: learn.dpu.surface-support-service-provider.use-customer-tenant-to-manage-surface-support
3+
title: Use a customer's tenant to manage Surface support
4+
metadata:
5+
title: Use A Customer's Tenant To Manage Surface Support
6+
description: This content is part of the "Managing Surface support as a service provider or partner" module.
7+
ms.date: 04/20/2026
8+
author: ozahran7
9+
ms.author: v-zahranomar
10+
ms.topic: unit
11+
durationInMinutes: 1
12+
content: |
13+
[!include[](includes/3-use-customer-tenant-to-manage-surface-support.md)]
Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
### YamlMime:ModuleUnit
2+
uid: learn.dpu.surface-support-service-provider.use-a-partner-tenant-to-manage-surface-support
3+
title: Use a partner tenant to manage Surface support
4+
metadata:
5+
title: Use A Partner Tenant To Manage Surface Support
6+
description: This content is part of the "Managing Surface support as a service provider or partner" module.
7+
ms.date: 04/20/2026
8+
author: ozahran7
9+
ms.author: v-zahranomar
10+
ms.topic: unit
11+
durationInMinutes: 1
12+
content: |
13+
[!include[](includes/4-use-a-partner-tenant-to-manage-surface-support.md)]
Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
### YamlMime:ModuleUnit
2+
uid: learn.dpu.surface-support-service-provider.manage-multiple-customer-tenants-safely
3+
title: Manage multiple customer tenants safely
4+
metadata:
5+
title: Manage Multiple Customer Tenants Safely
6+
description: This content is part of the "Managing Surface support as a service provider or partner" module.
7+
ms.date: 04/20/2026
8+
author: ozahran7
9+
ms.author: v-zahranomar
10+
ms.topic: unit
11+
durationInMinutes: 1
12+
content: |
13+
[!include[](includes/5-manage-multiple-customer-tenants-safely.md)]
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
### YamlMime:ModuleUnit
2+
uid: learn.dpu.surface-support-service-provider.understand-partner-boundaries-and-escalation-paths
3+
title: Understand partner boundaries and escalation paths
4+
metadata:
5+
title: Understand Partner Boundaries And Escalation Paths
6+
description: This content is part of the "Managing Surface support as a service provider or partner" module.
7+
ms.date: 04/20/2026
8+
author: ozahran7
9+
ms.author: v-zahranomar
10+
ms.topic: unit
11+
durationInMinutes: 1
12+
content: |
13+
[!include[](includes/6-understand-partner-boundaries-and-escalation-paths.md)]
Lines changed: 84 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,84 @@
1+
### YamlMime:ModuleUnit
2+
uid: learn.dpu.surface-support-service-provider.knowledge-check
3+
title: Knowledge check
4+
metadata:
5+
title: Knowledge Check
6+
description: This content is part of the "Managing Surface support as a service provider or partner" module.
7+
ms.date: 04/20/2026
8+
author: ozahran7
9+
ms.author: v-zahranomar
10+
ms.topic: unit
11+
durationInMinutes: 5
12+
quiz:
13+
title: Check your knowledge
14+
questions:
15+
- content: "Where should partners usually manage Surface service and support for a customer who already has an existing Microsoft tenant?"
16+
choices:
17+
- content: "Customer’s tenant"
18+
isCorrect: true
19+
explanation: "Correct. In most scenarios, partners manage Surface service and support by accessing the customer’s Microsoft tenant in Surface Support Portal so service history and tracking remain with the customer."
20+
- content: "Partner’s tenant"
21+
isCorrect: false
22+
explanation: "Incorrect. Using a partner tenant applies only to limited scenarios and isn't the most common approach."
23+
- content: "A newly created tenant"
24+
isCorrect: false
25+
explanation: "Incorrect. The module advises requesting access in the customer’s existing tenant rather than creating a new one."
26+
- content: "Surface Management Portal tenant"
27+
isCorrect: false
28+
explanation: "Incorrect. Surface Management Portal isn't a tenant used to manage Surface service and support."
29+
- content: "Which portal is used by partners to submit and track Surface service and support requests?"
30+
choices:
31+
- content: "Surface Management Portal"
32+
isCorrect: false
33+
explanation: "Incorrect. It can initiate some service actions but isn't the primary portal for partner workflows."
34+
- content: "Microsoft Intune"
35+
isCorrect: false
36+
explanation: "Incorrect. Intune doesn't handle Surface service and support requests."
37+
- content: "Surface Support Portal"
38+
isCorrect: true
39+
explanation: "Correct. Partner workflows for submitting and tracking service and support requests are centered in Surface Support Portal."
40+
- content: "Microsoft 365 Admin Center"
41+
isCorrect: false
42+
explanation: "Incorrect. It isn't used for Surface service and support management."
43+
- content: "What must partners confirm before creating a service order when managing multiple customer tenants?"
44+
choices:
45+
- content: "That the device is enrolled in Intune"
46+
isCorrect: false
47+
explanation: "Incorrect. Device enrollment isn't required to validate tenant context."
48+
- content: "That the correct tenant context is selected"
49+
isCorrect: true
50+
explanation: "Correct. Surface Support Portal is tenant-scoped, so partners must confirm the correct tenant before submitting requests."
51+
- content: "That shipping information is finalized"
52+
isCorrect: false
53+
explanation: "Incorrect. Shipping details come after tenant validation."
54+
- content: "That Surface Management Portal is accessible"
55+
isCorrect: false
56+
explanation: "Incorrect. Surface Management Portal access isn't required for submitting requests in Surface Support Portal."
57+
- content: "When is it appropriate for a partner to use their own tenant to manage Surface service and support?"
58+
choices:
59+
- content: "When the customer already has Surface Support Portal access"
60+
isCorrect: false
61+
explanation: "Incorrect. In this case, partners should work within the customer’s tenant."
62+
- content: "When the partner centrally manages service requests for multiple customers"
63+
isCorrect: true
64+
explanation: "Correct. The module identifies this as a scenario where using a partner tenant is appropriate."
65+
- content: "When the device is managed through Intune"
66+
isCorrect: false
67+
explanation: "Incorrect. Intune management doesn't determine which tenant to use for support."
68+
- content: "When the customer wants direct visibility into service tracking"
69+
isCorrect: false
70+
explanation: "Incorrect. Using a partner tenant may reduce direct customer visibility."
71+
- content: "Which statement correctly describes how Surface service and support requests are tracked?"
72+
choices:
73+
- content: "Service tracking is performed in Surface Management Portal"
74+
isCorrect: false
75+
explanation: "Incorrect. Surface Management Portal isn't used to track service and support requests."
76+
- content: "Requests are tracked within the tenant where they're submitted in Surface Support Portal"
77+
isCorrect: true
78+
explanation: "Correct. Requests are tenant-scoped and tracked in the tenant context used for submission."
79+
- content: "Service requests are automatically visible across all tenants"
80+
isCorrect: false
81+
explanation: "Incorrect. Requests aren't shared across tenants."
82+
- content: "Tracking depends on whether the device is Intune-enrolled"
83+
isCorrect: false
84+
explanation: "Incorrect. Tracking depends on tenant context, not device enrollment."
Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
### YamlMime:ModuleUnit
2+
uid: learn.dpu.surface-support-service-provider.summary
3+
title: Summary
4+
metadata:
5+
title: Summary
6+
description: This content is part of the "Managing Surface support as a service provider or partner" module.
7+
ms.date: 04/20/2026
8+
author: ozahran7
9+
ms.author: v-zahranomar
10+
ms.topic: unit
11+
durationInMinutes: 1
12+
content: |
13+
[!include[](includes/8-summary.md)]

0 commit comments

Comments
 (0)