Patient data systems, compliance reporting, and workflow automation for regulated environments.
Real-time tracking, route optimization, and inventory visibility across your distribution network.
Scale your product infrastructure, integrate third-party tools, and ship features faster with reliable ops.
Secure transaction processing, regulatory reporting, and customer-facing portals for financial services.
Azure AI Foundry is reshaping how enterprise teams build, deploy, and govern AI at scale, and the comparison with AWS Bedrock has become one of the defining platform decisions of 2025. If your organization runs on Microsoft 365, Teams, or Dynamics 365, or if you're planning azure cloud migration services in the near term, the platform you choose here will affect every AI workload you build for the next five years.
This post cuts through the marketing to compare both platforms on model selection, developer tooling, enterprise security, cost, and real-world fit for Microsoft-ecosystem businesses. We'll also answer the PAA questions that IT leaders keep searching for, including whether Azure is cheaper than AWS for enterprise and what an Azure managed services provider actually does.
Azure AI Foundry is Microsoft's unified platform for building AI applications and agents across the enterprise. It replaces the older Azure AI Studio and consolidates model access, prompt engineering, agent orchestration, and deployment governance into a single portal and SDK. You can access the azure ai foundry portal directly at ai.azure.com, and it sits inside your existing Azure subscription with full RBAC inherited from Azure Active Directory.
AWS Bedrock is Amazon's managed service for accessing foundation models from providers like Anthropic, Meta, Cohere, and Amazon's own Titan family. It emphasizes API-first model access with guardrails and knowledge base integrations built on S3 and Lambda.
The honest difference: Azure AI Foundry is a full development platform with project-level organization, agent lifecycle management, and deep Microsoft identity integration. AWS Bedrock is more narrowly focused on managed model APIs with solid AWS ecosystem glue. That distinction matters depending on what your team is actually trying to build.
Azure AI Foundry introduced two structural concepts that separate it from standalone model API services. The AI Hub is the organizational container for shared resources: compute, connections, policies, and governance settings. AI Projects sit inside the Hub and represent individual applications or workloads, each with their own model deployments, data connections, and evaluation pipelines. This is a meaningful architectural difference from AWS Bedrock, where account-level IAM handles most of what Azure Foundry handles at the Hub and Project layer.
The azure ai foundry sdk supports Python and JavaScript, with built-in Prompt Flow tooling for chaining model calls with retrieval-augmented generation. Azure AI Foundry agents, generally available in 2025, support multi-step agentic workflows with tool use, memory, and human-in-the-loop approval gates. For teams already using Power Automate consulting workflows, the agent integration with Azure Logic Apps and Power Platform opens automation scenarios that AWS simply can't match natively.
AWS Bedrock gives you API access to models from Anthropic (Claude), Meta (Llama), Mistral, Cohere, and Amazon Titan. Its Bedrock Agents feature supports similar agentic patterns, and Knowledge Bases connect to S3 or OpenSearch for RAG. The Bedrock Guardrails feature for content filtering is mature and well-documented, and it's genuinely one of the stronger safety control implementations available today.
Where Bedrock has a clear edge: if your infrastructure already lives on AWS, the IAM integration, VPC endpoints, and native S3 connectivity reduce friction considerably. Teams that are AWS-native and have no Microsoft ecosystem dependencies often find Bedrock simpler to start with.
| Feature | Azure AI Foundry | AWS Bedrock |
|---|---|---|
| Model catalog | 1,700+ models (GPT-4o, Phi-4, Mistral, Llama, Cohere) | ~40 models (Claude, Titan, Llama, Mistral, Cohere) |
| Proprietary models | GPT-4o, o3, Phi-4 (Microsoft/OpenAI partnership) | Amazon Titan only |
| Agent framework | Azure AI Foundry Agents (GA 2025) | Bedrock Agents |
| RAG support | Prompt Flow + Azure AI Search | Knowledge Bases + S3/OpenSearch |
| SDK | Azure AI Foundry SDK (Python, JS) | Boto3, Bedrock SDK |
| Human-in-the-loop | Native approval gates | Custom Lambda integration |
| Microsoft 365 integration | Native (Copilot Studio, Teams, Power Platform) | Via third-party connectors |
| Compliance certifications | FedRAMP High, HIPAA, ISO 27001, SOC 2 | FedRAMP, HIPAA, ISO 27001, SOC 2 |
| Fine-tuning | Yes (Azure OpenAI fine-tune + custom model catalog) | Yes (selected models only) |
| Pricing model | Pay-per-token + provisioned throughput units | Pay-per-token + provisioned |
| azure ai foundry documentation | Extensive, unified across all services | Per-service AWS docs |
The model count difference is real and it matters. Azure AI Foundry's catalog includes Hugging Face models, open-source checkpoints, and the full OpenAI lineup including GPT-4o and the reasoning-focused o3 model. If your team needs specialized models for healthcare NLP, code generation, or multilingual document processing, the selection is meaningfully wider.
AWS Bedrock's catalog is curated and smaller, but Anthropic Claude 3.5 and Claude 3 Opus are excellent for long-context document analysis tasks. For teams doing heavy PDF processing or legal document review, Bedrock's Claude integration is genuinely competitive on quality.
Azure AI Foundry documentation covers the full development lifecycle from model selection through evaluation, deployment, and monitoring. The Prompt Flow visual editor lowers the barrier for non-ML engineers to build RAG pipelines. The azure ai foundry sdk also includes built-in red teaming and safety evaluation tools, which matter for regulated industries that need documented evidence of pre-deployment testing.
AWS Bedrock relies more on the existing AWS toolchain. Teams fluent in CloudFormation, CDK, and Lambda find the integration natural. For teams primarily using .NET and Azure DevOps, the learning curve on Bedrock's toolchain is steeper.
Azure ai foundry pricing follows a consumption model: you pay per token for each model call, with rates varying by model tier. GPT-4o input tokens run approximately $2.50 per million tokens as of mid-2025, with provisioned throughput units available for predictable high-volume workloads.
Key Insight GPT-4o input tokens run approximately $2.50 per million tokens as of mid-2025, with provisioned throughput units available for predictable high-volume workloads.
One thing many teams miss when doing azure cost optimization consulting before an AI buildout: azure ai foundry cost includes not just model inference, but Azure AI Search indexing fees for RAG pipelines and compute costs for fine-tuning jobs. A complete budget should account for all three layers.
For a mid-market company running 10 million tokens per day across a customer-facing AI assistant, expect Azure AI Foundry costs between $8,000 and $25,000 per month depending on model choice and whether you're using provisioned capacity. The wide range reflects the difference between running Phi-4 (significantly cheaper) versus GPT-4o (premium pricing).
Key Insight For a mid-market company running 10 million tokens per day across a customer-facing AI assistant, expect Azure AI Foundry costs between $8,000 and $25,000 per month depending on model choice and whether you're using provisioned capacity.
Provisioned throughput is worth considering for any workload above 5 million tokens per day. The upfront commitment is higher, but it removes throttling risk during peak usage and often reduces per-token cost by 20-40% versus on-demand.
Key Insight The upfront commitment is higher, but it removes throttling risk during peak usage and often reduces per-token cost by 20-40% versus on-demand.
AWS Bedrock's per-token costs are comparable to Azure for equivalent models. Claude 3.5 Sonnet on Bedrock runs $3.00 per million input tokens. The ecosystem costs are where the comparison gets interesting. Organizations already running S3, CloudWatch, and Lambda often find that Bedrock adds less marginal infrastructure cost. Organizations not on AWS face onboarding overhead that Azure teams avoid.
According to Gartner research on cloud AI platform selection, total cost of ownership comparisons between Azure and AWS AI services depend heavily on your existing cloud estate and negotiated enterprise agreements. List price comparisons miss the full picture.
For Microsoft-ecosystem enterprises, yes, Azure AI Foundry wins. For AWS-native teams with no Microsoft dependencies, the decision is genuinely closer.
Azure AI Foundry is the stronger choice when your organization already uses Azure Active Directory, Microsoft 365, Dynamics 365, or Power Platform. The identity and access management integration means AI applications inherit the same RBAC policies your teams already manage. No identity federation work, no additional IAM complexity.
It also wins for teams doing azure app modernization alongside AI adoption. Deploying AI-powered features into .NET applications via the Azure AI Foundry SDK, with Azure DevOps pipelines handling CI/CD, is a workflow that requires zero additional cloud accounts or credential management.
The human-in-the-loop governance story is another genuine differentiator. As we covered in our post on AI agent governance, regulated industries need documented evidence that a human reviewed AI decisions before consequential actions. Azure AI Foundry's native approval gates make that auditable without custom middleware.
If your data lake is on S3, your compute is on EC2 or EKS, and your team has no Microsoft footprint, Bedrock genuinely reduces architectural complexity. The model quality (especially Claude) is excellent for document-heavy workloads, and Bedrock Guardrails for content filtering is mature and well-tested.
For teams building AI features on top of existing AWS microservices, Bedrock integrates more naturally than adding Azure as a second cloud provider. The integration tax of running two major cloud platforms is real, and it's a legitimate reason to stay on Bedrock even if Azure AI Foundry's catalog is larger.
The most common question we hear from teams that want to move to Azure AI Foundry: how do we get there from on-premises or from AWS? The answer depends on your starting point, but azure landing zone implementation is almost always the first technical milestone.
An Azure landing zone is the configured, policy-governed Azure environment into which workloads are deployed. Microsoft's Cloud Adoption Framework defines two primary archetypes: Start Small and Expand for organizations beginning their journey, and Enterprise Scale for complex governance requirements.
For most mid-market companies starting an azure infrastructure assessment, the enterprise scale landing zone is overkill initially. A pragmatic approach starts with three management groups (Platform, Landing Zones, Sandbox), implements Azure Policy for tagging and compliance baselines, and uses Azure Blueprints to enforce security configurations. The landing zone design phase typically takes two to four weeks and produces the governance architecture that every subsequent workload builds on.
QServices has completed 500+ Azure and Microsoft platform projects since 2014 as a Microsoft Certified Solutions Partner specializing in Azure. Landing zone implementations we've delivered for healthcare and banking clients consistently reduce remediation work at the compliance audit stage by a meaningful margin.
The lift and shift to azure approach moves workloads to Azure VMs without significant refactoring. It's fast, low-risk, and removes on-premises hardware dependencies quickly. The tradeoff: you don't benefit from PaaS services like Azure App Service, Azure SQL Managed Instance, or Azure AI Foundry APIs until you refactor.
For organizations whose primary goal is accessing Azure AI Foundry, a hybrid cloud azure setup often makes sense as an intermediate state. Lift and shift the core application infrastructure first, then refactor AI workloads to consume Azure AI Foundry APIs while the remaining stack migrates on its own timeline.
Azure devops consulting services become critical at this stage. The CI/CD pipeline needs to handle both legacy VM deployments and new container-based or serverless AI workloads, often simultaneously. Our Azure Pipelines YAML guide covers the pipeline configuration patterns that work well for teams in this transition.
Migrate on premise to azure rarely happens in a single event. Most mid-market companies take six to eighteen months from initial azure architecture review to having all workloads running in Azure. The five phases of Azure migration are: Discover and Assess, Plan, Migrate, Optimize, and Govern.
The discovery phase inventories every server, database, application dependency, and network connection in your current environment. Azure Migrate is the native tooling, generating a readiness report with recommended Azure SKUs and estimated monthly costs. An azure infrastructure assessment done properly takes three to six weeks and produces a migration wave plan that sequences workloads by complexity and risk.
Stateless applications migrate first. Databases with complex schemas, high-transaction workloads, and applications with tight latency requirements migrate last after dependency mapping is complete.
After migration, most organizations lack the internal headcount to monitor, patch, optimize, and respond to incidents in their Azure environment on an ongoing basis. An azure managed services provider handles that operational layer: security patching, cost analysis, performance monitoring, incident response, and capacity planning.
The microsoft azure consulting company relationship shifts from project-based to ongoing partnership. A good Azure managed services provider typically reduces cloud spend by 15-30% in the first year through reserved instance purchasing, right-sizing, and idle resource cleanup. That's the kind of azure cost optimization consulting that pays for itself.
One reason Microsoft-ecosystem businesses choose Azure AI Foundry over AWS Bedrock: native integration with Power Platform. Power automate consulting teams can connect Azure AI Foundry models directly to Power Automate flows without custom middleware. Power BI consulting services can incorporate AI-generated insights into dashboards via direct Azure AI Foundry API calls. Power apps development services can embed AI-powered document summarization or image classification features with minimal backend code.
The Power Platform governance story benefits from Azure AI Foundry too. Data Loss Prevention policies, Managed Environments, and Azure Policy all operate from the same admin center. Power platform governance and AI governance converge in a way that doesn't happen when you bolt AWS Bedrock onto a Microsoft stack.
As a power platform development company, QServices regularly implements Power Apps development services alongside Azure AI Foundry projects. The combined workflow, where a Power App captures user input, passes it to an Azure AI Foundry agent, and writes the result back to a SharePoint list via Power Automate, takes days to build rather than weeks.
Deploying AI in regulated industries requires demonstrating that AI workloads meet the same security standards as the rest of your infrastructure. An azure security assessment for AI specifically reviews network segmentation (are AI endpoints in a private VNet?), identity controls (are service principals scoped to least privilege?), data handling (is training data encrypted at rest and in transit?), and audit logging (is every model call captured in Azure Monitor?).
Azure AI Foundry passes data to OpenAI models via Microsoft's private network backbone by default, meaning customer data doesn't traverse the public internet. That's a compliance advantage for HIPAA and PCI-DSS workloads that AWS Bedrock also offers via PrivateLink, though the configuration is more involved on the AWS side. Microsoft's data privacy documentation covers the data residency and processing boundaries in detail.
Human-in-the-Loop governance ensures human approval at every deployment stage for AI workloads in sensitive domains. This isn't optional for most regulated enterprises, and Azure AI Foundry's native implementation of this pattern is more integrated than what's available on AWS Bedrock today.
QServices has completed 500+ Azure and Microsoft platform projects since 2014. As a microsoft azure consulting company and azure migration partner with certified architects across Azure, Power Platform, and Dynamics 365, we work with mid-market and enterprise clients in healthcare, banking, logistics, and SaaS.
Our azure consulting services cover the full adoption journey: initial azure infrastructure assessment and azure architecture review, azure cloud migration services execution, Azure AI Foundry project setup and agent development, power platform development company work for automation and apps, and ongoing azure managed services provider support.
If you're comparing Azure AI Foundry against AWS Bedrock and want an honest assessment of which platform fits your current stack and roadmap, our Cloud AI Strategy Call is a 60-minute working session with a certified Azure architect. We'll review your environment, identify quick wins, and give you a clear recommendation with realistic timeline and budget estimates. Book a Cloud AI Strategy Call to get started.
Azure AI Foundry wins for Microsoft-ecosystem enterprises on the dimensions that matter most: model catalog depth, developer tooling maturity, Power Platform integration, governance controls, and compliance posture for regulated industries. AWS Bedrock remains a strong platform for AWS-native teams, particularly for Claude-powered document processing workloads.
The azure cloud migration services decision and the AI platform decision are increasingly the same decision in 2025. How you structure your Azure landing zone, how you approach azure cost optimization consulting, and how you set up power platform governance all determine how much value you extract from Azure AI Foundry in production.
QServices is ready to help you make that decision and execute on it. Book a Cloud AI Strategy Call with our azure consulting services team to map your migration path and Azure AI Foundry adoption plan. We'll review your current infrastructure, flag the risks, and give you a timeline you can actually hold to.
Written by Rohit Dabra
Co-Founder and CTO, QServices IT Solutions Pvt Ltd
Rohit Dabra is the Co-Founder and Chief Technology Officer at QServices, a software development company focused on building practical digital solutions for businesses. At QServices, Rohit works closely with startups and growing businesses to design and develop web platforms, mobile applications, and scalable cloud systems. He is particularly interested in automation and artificial intelligence, building systems that automate routine tasks for teams and organizations.
Talk to Our ExpertsAzure AI Foundry is Microsoft’s unified platform for building, deploying, and governing enterprise AI applications and agents. It consolidates model access (1,700+ models including GPT-4o and Phi-4), prompt engineering, agent orchestration, and deployment governance into a single portal and SDK. It replaces Azure AI Studio and sits inside your existing Azure subscription with full identity integration via Azure Active Directory.
Azure AI Foundry includes several core tools: the AI Hub for managing shared resources and governance policies, AI Projects for organizing individual AI workloads, Prompt Flow for building RAG and chain-of-thought pipelines, Azure AI Foundry Agents for multi-step agentic workflows with tool use and memory, built-in safety evaluation and red teaming tools, and the Azure AI Foundry SDK for Python and JavaScript development.
Azure AI Hub is a component within Azure AI Foundry, not a separate product. The Hub is the organizational container that holds shared compute, connections, governance policies, and management group settings. Azure AI Foundry is the overall platform that includes the Hub, individual AI Projects (which sit inside a Hub), the model catalog, Prompt Flow, agent framework, and the developer portal. Think of the Hub as the governance layer and Foundry as the complete development environment.
Copilot Studio is a low-code tool for building conversational AI assistants and copilots, primarily for business users and Power Platform developers. It uses pre-built connectors and a visual interface. Azure AI Foundry is a full developer platform for building custom AI applications, fine-tuning models, creating agentic workflows, and deploying AI services at enterprise scale. Copilot Studio suits business-led automation; Azure AI Foundry suits engineering teams building custom AI products.
Azure cloud migration typically costs between $50,000 and $500,000 for mid-market companies, depending on the number of workloads, complexity of database migrations, and whether the approach is lift-and-shift or cloud-native refactoring. Ongoing Azure managed services provider costs typically run 10-20% of annual cloud spend. An initial azure infrastructure assessment, which scopes the migration accurately, usually costs $15,000 to $40,000 and produces a detailed wave plan with SKU recommendations and budget estimates.
The honest answer is it depends on your existing cloud estate and enterprise agreements. For organizations already paying for Microsoft 365 and Dynamics 365, Azure typically offers better consolidated pricing through Microsoft’s enterprise agreement structure. For purely compute and storage workloads with no Microsoft dependencies, AWS can be competitively priced. According to Gartner, total cost of ownership comparisons must account for migration costs, staff retraining, integration work, and negotiated discounts, not just list-price compute rates.
An Azure managed services provider handles ongoing operational management of your Azure environment after migration. This includes security patching and update management, 24/7 monitoring and incident response, cost optimization through reserved instance purchasing and right-sizing, capacity planning, compliance reporting, and Azure architecture reviews as your workloads evolve. A good Azure managed services provider typically reduces cloud spend by 15-30% in the first year through proactive optimization, and ensures your environment stays compliant with changing regulatory requirements.
Azure Integration Services Explained: Logic Apps, Service Bus, API Management, and Event Grid Rohit Dabra | July 10, 2026 Table
Power BI Embedded is Microsoft’s developer-focused API for embedding interactive analytics directly inside third-party apps, customer portals, and SaaS products. If you are building software and want customers to see live dashboards without logging into the Power BI service, this is where that journey starts. The question is not whether you can embed Power BI reports, you almost certainly can. The real question is whether it makes financial and architectural sense for your specific situation. This guide covers the when, the how, and the cost math that most tutorials skip.
Power apps portals sit at an interesting crossroads for IT leaders: they’re fast, deeply integrated with the Microsoft stack, and manageable without a dedicated development team. But they’re also constrained in ways that matter when your business needs a portal that handles complex UI logic, third-party integrations outside the Microsoft ecosystem, or pixel-perfect UX design.
This guide gives you a straight comparison so you can make the right call without spending three months in discovery. We’ll cover what each option actually delivers, where each breaks down, and the governance questions that need answers before you commit either way.
If you’re evaluating your Microsoft stack more broadly, our breakdown of Power Platform vs Custom .NET Development provides useful parallel context.
Azure AI Foundry is reshaping how enterprise teams build, deploy, and govern AI at scale, and the comparison with AWS Bedrock has become one of the defining platform decisions of 2025. If your organization runs on Microsoft 365, Teams, or Dynamics 365, or if you’re planning azure cloud migration services in the near term, the platform you choose here will affect every AI workload you build for the next five years.
This post cuts through the marketing to compare both platforms on model selection, developer tooling, enterprise security, cost, and real-world fit for Microsoft-ecosystem businesses. We’ll also answer the PAA questions that IT leaders keep searching for, including whether Azure is cheaper than AWS for enterprise and what an Azure managed services provider actually does.
React Native is a cross-platform framework built by Meta that allows development teams to write a shared JavaScript codebase and deploy to both iOS and Android. For enterprise architects evaluating mobile strategy in 2025, the choice between react native development, Flutter, and Xamarin goes well beyond which syntax your team prefers. It touches deployment timelines, maintenance costs, existing skill sets, and how tightly the front end needs to connect to your backend infrastructure.
This post breaks down all three frameworks across performance, developer experience, enterprise support, and Azure cloud integration. By the end, you’ll have a clear picture of which framework fits your organization, and when alternatives like Power Apps make more sense than a custom mobile build.
AI agent governance is the practice of establishing policies, controls, and human oversight mechanisms that determine how AI agents operate, make decisions, and interact with business systems. For enterprises deploying AI today, this isn’t optional paperwork. It’s the difference between AI that delivers measurable value and AI that creates liability.
The pressure to ship AI quickly is real. Microsoft Copilot, Azure OpenAI, and Power Platform’s AI Builder have made it easier than ever to wire autonomous agents into workflows. But “easy to deploy” doesn’t mean “safe to leave unsupervised.” Every enterprise that skipped governance in the rush to launch has eventually paid for it, whether through data leaks, compliance failures, or decisions no one can explain to an auditor.
This post covers why human-in-the-loop (HITL) oversight is non-negotiable for enterprise AI, what a real governance framework looks like, and how QServices approaches this with clients across healthcare, banking, and logistics.
Power BI Embedded is Microsoft’s developer-focused API for embedding interactive analytics directly inside third-party apps, customer portals, and SaaS products. If you are building software and want customers to see live dashboards without logging into the Power BI service, this is where that journey starts. The question is not whether you can embed Power BI reports, you almost certainly can. The real question is whether it makes financial and architectural sense for your specific situation. This guide covers the when, the how, and the cost math that most tutorials skip.
Power apps portals sit at an interesting crossroads for IT leaders: they’re fast, deeply integrated with the Microsoft stack, and manageable without a dedicated development team. But they’re also constrained in ways that matter when your business needs a portal that handles complex UI logic, third-party integrations outside the Microsoft ecosystem, or pixel-perfect UX design.
This guide gives you a straight comparison so you can make the right call without spending three months in discovery. We’ll cover what each option actually delivers, where each breaks down, and the governance questions that need answers before you commit either way.
If you’re evaluating your Microsoft stack more broadly, our breakdown of Power Platform vs Custom .NET Development provides useful parallel context.
Azure AI Foundry is reshaping how enterprise teams build, deploy, and govern AI at scale, and the comparison with AWS Bedrock has become one of the defining platform decisions of 2025. If your organization runs on Microsoft 365, Teams, or Dynamics 365, or if you’re planning azure cloud migration services in the near term, the platform you choose here will affect every AI workload you build for the next five years.
This post cuts through the marketing to compare both platforms on model selection, developer tooling, enterprise security, cost, and real-world fit for Microsoft-ecosystem businesses. We’ll also answer the PAA questions that IT leaders keep searching for, including whether Azure is cheaper than AWS for enterprise and what an Azure managed services provider actually does.
React Native is a cross-platform framework built by Meta that allows development teams to write a shared JavaScript codebase and deploy to both iOS and Android. For enterprise architects evaluating mobile strategy in 2025, the choice between react native development, Flutter, and Xamarin goes well beyond which syntax your team prefers. It touches deployment timelines, maintenance costs, existing skill sets, and how tightly the front end needs to connect to your backend infrastructure.
This post breaks down all three frameworks across performance, developer experience, enterprise support, and Azure cloud integration. By the end, you’ll have a clear picture of which framework fits your organization, and when alternatives like Power Apps make more sense than a custom mobile build.
AI agent governance is the practice of establishing policies, controls, and human oversight mechanisms that determine how AI agents operate, make decisions, and interact with business systems. For enterprises deploying AI today, this isn’t optional paperwork. It’s the difference between AI that delivers measurable value and AI that creates liability.
The pressure to ship AI quickly is real. Microsoft Copilot, Azure OpenAI, and Power Platform’s AI Builder have made it easier than ever to wire autonomous agents into workflows. But “easy to deploy” doesn’t mean “safe to leave unsupervised.” Every enterprise that skipped governance in the rush to launch has eventually paid for it, whether through data leaks, compliance failures, or decisions no one can explain to an auditor.
This post covers why human-in-the-loop (HITL) oversight is non-negotiable for enterprise AI, what a real governance framework looks like, and how QServices approaches this with clients across healthcare, banking, and logistics.
Earning Global Recognition: A Testament to Quality Work and Client Satisfaction. Our Business Thrives on Customer Partnership
