MB-260T00: Microsoft Customer Insights – Data Specialty — Lesson 1: Customer Insights Architecture, Sources and Data Ingestion

Learning Objectives

• Explain Customer Insights environments, data sources, tables, refresh, profiles, activities, measures, segments, predictions, and destinations
• Connect approved sources, map fields, define primary keys, configure schedules, assess quality, and resolve ingestion errors
• Validate customer insights architecture, sources and data ingestion decisions with documented requirements, evidence, risk controls, and measurable acceptance criteria

Detailed Topics

• Explain Customer Insights environments: Explain Customer Insights environments, data sources, tables, refresh, profiles, activities, measures, segments, predictions, and destinations
• Connect approved sources: Connect approved sources, map fields, define primary keys, configure schedules, assess quality, and resolve ingestion errors
• Validate customer insights architecture: Validate customer insights architecture, sources and data ingestion decisions with documented requirements, evidence, risk controls, and measurable acceptance criteria

Guided Demonstration

1. Review the requirement, users, data, dependencies, permissions, risks, and expected result.
2. Demonstrate the relevant configuration, development, analysis, administration, testing, or operational workflow step by step.
3. Capture settings, outputs, logs, screenshots, calculations, test results, and other useful evidence.
4. Compare the observed result with acceptance criteria and explain any corrective action.

Hands-On Activity

Create a requirements and readiness checklist, then design or configure the first working foundation.

• Document assumptions, prerequisites, and the planned sequence before starting.
• Complete the activity and preserve evidence of normal, boundary, and failure behavior.
• Record issues, corrective actions, reusable notes, and the next improvement priority.

Scenario Analysis

• Identify the business or technical decision that must be made.
• Compare valid implementation approaches and their trade-offs.
• Consider security, privacy, accessibility, performance, support, and operational impact.

Troubleshooting Focus

• Separate symptoms from causes and collect evidence before applying a fix.
• Check configuration, data, permissions, dependencies, capacity, connectivity, and recent changes.
• Validate rollback, recovery, ownership, user impact, and business continuity.

Validation Checklist

• The requirement, scope, inputs, and expected outcome are clear.
• The selected design or configuration is documented and follows approved standards.
• Normal, boundary, failure, security, accessibility, and operational conditions are reviewed.
• The result is supported by evidence and the next improvement is prioritized.

Lesson Outcome

Learners can explain and apply Customer Insights Architecture, Sources and Data Ingestion in a realistic scenario and validate the result with documented evidence.