Core integration stack: Azure Service Bus → Platform Events (bidirectional event streaming), Azure Logic Apps → Salesforce REST/SOAP API (workflow automation without code), Azure AD → Salesforce SSO (Microsoft employees authenticate via Microsoft account), Power BI → Salesforce data connector (executive dashboards), Teams → Salesforce connector (CRM data in Teams channels) | Data sync: Salesforce → Azure Data Factory → Azure Synapse Analytics (data warehouse for analytics beyond CRMA) | Real-time: Azure Service Bus topics → Salesforce Platform Events (Azure-native equivalent of AWS EventBridge + SNS) | Security: Azure Key Vault stores Salesforce Connected App credentials (equivalent to AWS Secrets Manager) | Monitoring: Azure Monitor + Application Insights for integration health

Setup: Entra ID admin center → Enterprise Applications → Add Salesforce → configure SAML SSO → download federation metadata → upload to Salesforce SSO settings | Attribute mapping: user.userprincipalname → FederationIdentifier, user.department → Department, user.jobTitle → Title | JIT: SAML assertion includes attributes to create Salesforce user on first login | Groups: Microsoft 365 Groups or Entra ID Security Groups mapped to Salesforce Profiles/Permission Sets | Conditional Access: Entra ID Conditional Access Policy can require compliant device, specific location, MFA level before Salesforce SSO grants access | Microsoft Authenticator: satisfies Salesforce MFA requirement natively (no separate MFA tool needed) | Deprovisioning: user disabled in Entra ID → Salesforce session expires, manual deactivation still required | Note: rebranded from Azure AD to Microsoft Entra ID in 2023 — use Entra ID in Microsoft interviews

Salesforce for Teams: AppExchange app embedding Salesforce records in Teams tabs, notifications (Opportunity stage changed → Teams channel message), deal rooms (Teams channel per Opportunity with live data card), @mentions of Salesforce records in Teams chats | Meeting Intelligence: Teams premium + Conversation Intelligence — call transcribed, key moments highlighted, summary added to Salesforce Case/Opportunity activity | Teams bot: sales rep types @Salesforce lookup IBM → bot returns Account health card in Teams chat | Power Automate: connect Teams and Salesforce without code (new Opportunity → create Teams channel, Opportunity won → send Teams celebration message) | Microsoft Viva Sales: AI-powered sales experience embedding Salesforce in Teams and Outlook — Microsoft's strategic product for exactly this use case | Why important: Microsoft employees live in Teams — Salesforce must come to Teams, not the other way around

Use Power Automate when: connecting Salesforce to Microsoft 365 (new Salesforce Account → create SharePoint folder, Opportunity closed → update Excel tracking sheet, Case created → Teams notification) — Power Automate has native Microsoft connectors Salesforce Flows don't | Use Salesforce Flow when: CRM-specific automation (lead assignment, opportunity routing, case escalation) — Flows have CRM context Power Automate lacks | Use Power BI when: combining Salesforce data with Azure, Microsoft 365, LinkedIn, and other non-Salesforce data sources for executive analytics | Use CRMA when: Salesforce-only analytics with Einstein AI integration needed | Governance: avoid duplicate automation (same trigger in both Power Automate and Salesforce Flow causes double execution) | Architecture principle: Salesforce owns CRM logic, Power Platform owns Microsoft ecosystem integrations

Power BI Salesforce connector: Setup → Get Data → Salesforce Objects or Salesforce Reports → import or DirectQuery | DirectQuery: real-time data (slower queries, no transformation) vs Import (scheduled refresh, transformations available, faster) | Combined dataset: Salesforce Opportunity + Azure billing data + SharePoint contract status + LinkedIn company growth signals | DAX measures: custom calculations (ARR, NRR, win rate) in Power BI semantic model | Row-level security: Power BI RLS aligned to Salesforce role hierarchy (manager sees team data, rep sees own) | Scheduled refresh: Power BI Premium auto-refreshes Salesforce connection | When to use CRMA instead: real-time Salesforce-only data with Einstein insights, user-level Salesforce security automatic | Power BI Premium: required for large Salesforce datasets (>1M rows) and DirectQuery

Salesforce → Azure: Platform Event fired → CometD subscriber (Azure Function) → Service Bus topic → multiple Azure subscribers (Synapse, other services) | Azure → Salesforce: business event in Azure → Service Bus topic → Logic App trigger → Salesforce REST API upsert | Service Bus vs Event Hub: Service Bus for enterprise messaging (guaranteed delivery, dead letter, sessions), Event Hub for high-throughput telemetry (millions/second, stream processing via Stream Analytics) | Use Service Bus when: guaranteed delivery required, message ordering matters, dead letter queue for failures | Use Event Hub when: massive volume (IoT, clickstream), stream analytics | Logic Apps: low-code integration connecting Service Bus trigger → Salesforce action (no custom code needed for standard field mapping) | Dead letter: failed Salesforce API calls → Service Bus dead letter queue → Azure Monitor alert → retry workflow

Salesforce advantages: AppExchange (7,000+ apps), broader third-party ecosystem, more mature CPQ (Salesforce CPQ vs Dynamics 365 Commerce), stronger field service (FSL vs Dynamics 365 Field Service), better developer community/talent availability | Dynamics 365 advantages: native Microsoft integration (Teams, Outlook, Power Platform, Azure), Copilot AI (Microsoft 365 Copilot natively extends to Dynamics), simpler licensing (often included in existing Microsoft agreements), Power Platform no-code customization, Azure native data storage (no external API needed) | Migration cost: switching from established Salesforce org is expensive — data migration, retraining, integration rebuild | Honest Microsoft answer: choose based on business need, not brand loyalty — Growth Mindset requires this honesty | When Microsoft uses Salesforce: their own commercial division found migration cost/risk not justified for established Salesforce orgs

CRM Sync setup: Sales Navigator settings → CRM Integration → Salesforce → OAuth connection → enable sync | What syncs: Sales Navigator Leads → Salesforce Leads/Contacts, Sales Navigator Accounts → Salesforce Accounts, saved leads status | What surfaces in Salesforce: LinkedIn profile photo, job title, company, mutual connections, recent activity, TeamLink connections | InMail: messages sent via Sales Navigator → logged as Task on Salesforce Contact | Job change alerts: contact changes job → alert in Sales Navigator + can be surfaced in Salesforce via API | Microsoft synergy: Microsoft owns LinkedIn — this integration is exclusively better for Microsoft customers than it is for competitors | GDPR: LinkedIn data in Salesforce must comply with GDPR — member profile data cannot be stored longer than necessary | TeamLink: shows which colleagues are connected to a prospect — powerful warm introduction finder

Pipeline: Salesforce Bulk API → Azure Data Factory pipeline (scheduled nightly) → Azure Data Lake Storage Gen2 (raw zone) → Synapse Spark (data transformation, cleansing) → Synapse SQL Pool (analytics-ready) → Power BI DirectQuery | Real-time option: Salesforce CDC → Azure Event Hub → Synapse Analytics streaming | Unified dataset: Salesforce CRM + Azure billing data + Microsoft 365 engagement data + LinkedIn company data → single Synapse database → Power BI unified dashboard | Cost optimization: Synapse serverless SQL pools for ad-hoc queries (pay per TB scanned) vs dedicated pools for regular dashboards | Comparison to BigQuery: same concept, Microsoft ecosystem — Azure Data Factory = Google Cloud Data Transfer, Synapse = BigQuery, Power BI = Looker | Incremental load: use Salesforce SystemModstamp field for incremental data loads (only changed records)

Graph API capabilities: GET /users/{id}/messages (Outlook emails), GET /users/{id}/events (calendar), GET /teams/{teamId}/channels (Teams), GET /sites/{siteId}/lists (SharePoint), GET /me/drive/items (OneDrive) | Use case in Salesforce: LWC component on Account record → callout to Graph API → show last 5 emails with this account domain, Teams meeting history, shared SharePoint files | Authentication: Azure AD OAuth 2.0 app registration → client credentials flow → Named Credential in Salesforce stores token | Permissions: Graph API requires specific API permissions (Mail.Read, Calendars.Read, Files.Read) — request minimum needed | GDPR: Graph API returns personal data — must handle per GDPR (not store, only display) | Alternative: Microsoft Viva Sales does this automatically — but knowing Graph API implementation is important for architect roles

Logic Apps: drag-drop workflow, Salesforce connector built-in, 400+ connectors (SharePoint, Teams, Service Bus, Outlook), triggers (when Salesforce record created/updated), actions (create Teams channel, send Outlook email, update SharePoint list) | Use Logic Apps when: standard integration without complex logic, non-developer can maintain, standard Salesforce CRUD operations | Azure Functions: code-first (C#, Python, JS, Java), triggered by HTTP/Service Bus/Event Hub/Timer, complex transformation logic, custom error handling, unit-testable | Use Functions when: complex data transformation, high-performance requirement, custom retry logic, integration with multiple systems in one transaction | Cost: Logic Apps per-execution (cheaper for low-volume), Functions per-execution (cheaper for high-volume with consumption plan) | Hybrid: Logic Apps orchestrate the workflow, Functions handle complex transformation steps (Logic App calls Function for complex logic) | Salesforce connection: both support Salesforce REST API via HTTP connector

Entra ID Conditional Access: require compliant device (Intune-managed) + MFA before Salesforce SSO grants access — prevents access from unmanaged personal devices | Microsoft Sentinel: import Salesforce Event Monitoring logs → unified security dashboard with all Microsoft logs → AI-powered threat detection (unusual data export, impossible travel) | Microsoft Purview: classify Salesforce data (PII, confidential, public) → apply retention policies, DLP rules | Azure Key Vault: store Salesforce Connected App client secret → rotate automatically → no secrets in code | Salesforce Shield: encrypt sensitive fields (AES-256), event monitoring for audit, field audit trail for 10-year retention | DLP: Microsoft Purview DLP policy can prevent Salesforce data from being copied to non-compliant Teams channels | Zero Trust: verify explicitly (Entra ID), use least privileged access (Permission Sets), assume breach (Shield event monitoring)

Structure: what was the technology (something genuinely new, not just a new version), why you chose to learn it (business problem you saw, personal curiosity, future relevance), HOW you learned (Trailhead trail, YouTube, community forums, built in sandbox, attended webinar), how quickly you applied it (within weeks), and measurable outcome. Best examples: Agentforce (new 2024-2025), Data Cloud (growing), Flow Orchestration (relatively new) | Growth Mindset signals: you initiated the learning (not assigned), you learned from community (not just official docs), you shared what you learned with team, you applied it to real business problem | Avoid: "I learned Salesforce Admin certification" (basic, expected). "I learned a feature that was 5 years old" (not current learning)

Approach: (1) Ask clarifying questions — what does the division do, what Microsoft products are they already using, what is their team's technical capability, do they have existing Salesforce or Dynamics experience? (2) Evaluate: if Microsoft 365 deeply embedded → Dynamics 365 (native integration), if division has complex CPQ needs → Salesforce CPQ (more mature), if division already has Salesforce consultants → migration cost may outweigh Dynamics benefits, if division needs industry-specific cloud (Health Cloud, FSL) → Salesforce has more mature options, if cost is primary driver → Dynamics (often included in existing Microsoft licensing) (3) Recommendation with clear rationale and explicit trade-offs | Key: never say "always Dynamics" — that is NOT Growth Mindset. The correct answer is "it depends on specific requirements, and here are the factors I would evaluate."

Cross-team collaboration story: Salesforce team + Teams product team (or internal Teams admin team) → integrated Salesforce deal rooms into Teams channels. Setup: identified that reps lived in Teams but CRM was in Salesforce. Reached out to Teams admin proactively. Built: Teams connector showing live Opportunity data, stage change notifications to deal room channel, meeting summaries added to Salesforce activity via Teams meeting intelligence. Result: rep productivity improved, CRM data quality improved (activity logging increased from 34% to 89% because it happened automatically in Teams) | One Microsoft signal: you saw an integration opportunity across product boundaries, reached out proactively, built something that used both platforms better than either alone.

Growth Mindset failure story: what failed (specific, real, significant), what was YOUR contribution to the failure (Growth Mindset requires ownership, not blame), what you investigated to understand why (diving deep into the root cause), what you specifically learned (one actionable insight, not generic lessons), and how you applied it in the next project (specific outcome improvement) | Microsoft specific: they value people who talk openly about failure because psychological safety is important for innovation — if people hide failures, the organization cannot learn | Format: less structured than Amazon STAR — can be more conversational at Microsoft, but still needs clear narrative arc

Empathy story structure: discovery (how you found out users were struggling — observation, feedback, metrics, direct conversation), investigation (what you specifically did to understand their actual problem — shadowed them, interviewed them, analyzed usage data), design decision (what you chose to build based on their real needs vs what was easiest technically), implementation, result (user satisfaction metric, adoption rate, productivity improvement) | Microsoft empathy signal: you did not just fix the reported bug — you asked "why does this happen and what would make this genuinely easier?" | Best examples: simplified a complex Salesforce layout after watching reps struggle with 34 required fields (reduced to 8 most important), created mobile-optimized view after discovering 60% of reps were on mobile but UI was desktop-only

Questions first: does every rep use Teams? (Yes — it is Microsoft). Is Power BI already deployed? (Yes). What existing Azure services are used? | Architecture: Entra ID SSO (every Microsoft employee authenticates via Microsoft account, no separate Salesforce password), Teams integration (Salesforce records in Teams channels, deal rooms, meeting intelligence), Power BI (combined Salesforce + Azure analytics for executives — beyond CRMA), LinkedIn Sales Navigator CRM Sync (Microsoft-owned, deep integration), Service Bus (Azure → Salesforce event streaming), Viva Sales (AI-powered selling experience in Teams/Outlook with Salesforce backend), Shield (enterprise encryption + event monitoring for Microsoft's compliance requirements) | Unique Microsoft advantage: Entra ID + Conditional Access (device compliance required), Viva Sales (Microsoft-specific AI sales assistant), LinkedIn integration (Microsoft-owned network)

Data architecture: Salesforce → Azure Data Factory → Azure Data Lake Storage (raw) → Synapse Spark (clean/transform) → Synapse SQL Pool (analytics layer) | Dynamics 365 → Azure Synapse Link (native, real-time, no Data Factory needed — this is a key Dynamics advantage) | Azure operational data: direct connection to Synapse | Unified customer model: one row per customer with attributes from all systems (Salesforce Account.ARR, Dynamics Opportunity.Stage, Azure subscription status) | Identity resolution: match customers across Salesforce and Dynamics by email domain, company name fuzzy match, or common identifier | Power BI: customer 360 dashboard showing all signals regardless of source system | Conflict: same customer record updated in both Salesforce and Dynamics — need MDM policy (which system is master for which field) | Microsoft Purview: data catalog documenting lineage of customer data across all three systems

Rep workflow without opening Salesforce: Morning briefing (Power Automate sends Teams message with deals closing this week), Deal update (rep changes Opportunity stage in Teams tab — syncs to Salesforce), Meeting prep (Viva Sales surfaces customer context in Teams meeting before it starts), Meeting notes (Teams meeting intelligence auto-logs summary to Salesforce activity), Approvals (Salesforce approval request appears as Teams notification — manager approves in Teams), Deal win (Opportunity closed → Teams celebration card in team channel) | What still requires Salesforce: complex report building, admin configuration, bulk data operations, CPQ quote building | Success metric: # of Salesforce logins per week per rep (target: reduce by 70% while maintaining data quality) | Viva Sales: Microsoft's AI copilot specifically designed for this Teams-first sales experience — mention it explicitly

Shadow IT problem: business users create Power Automate flows connecting Teams to Salesforce — good intent but no error handling, no testing, no documentation, duplicate automation with existing Salesforce Flows | CoE Starter Kit: Microsoft-provided governance framework for Power Platform — deploy it to your tenant for monitoring, approval workflows for new flows, usage analytics | DLP Policies: define which connectors can be used together (allow Salesforce connector only in approved environments) | Environment Strategy: Production environment (IT-managed), Departmental (business-managed with IT guardrails), Developer (individual sandboxes) | Managed Environments: Enterprise-grade governance features — Sharing Limits (flow cannot be shared with more than 20 people without IT review), Solution Checker (code quality) | Approval Process: business team proposes new Power Platform-Salesforce integration → IT reviews for duplication, security, performance → approved → deployed to managed environment | Monitoring: Power Platform admin center shows all flows using Salesforce connector — review weekly for unsanctioned connections