Deployment Types in AI Foundry

Deploying a model in Azure AI Foundry can be done in 9 different ways.  Depending on the type of deployment chosen, it may impact one of more factors, such as cost, latency, efficiency for processing large datasets, compliance.  Listed below is a description of each deployment type, along with advantages and disadvantages.  For more details, please visit https://learn.microsoft.com/en-us/azure/ai-foundry/foundry-models/concepts/deployment-types

Deployment Type	Description	Advantage	Disadvantage
Global Standard	Shared global infrastructure for general-purpose model inference.	Cost-effective and easy to scale.	Performance may vary under high demand.
Global Provisioned	Dedicated global infrastructure for consistent performance.	Reliable throughput and latency.	Higher cost due to dedicated resources.
Global Batch	Asynchronous global batch processing for large-scale inference jobs.	Efficient for processing large datasets.	Not suitable for real-time applications.
Data Zone Standard	Shared infrastructure within a specific data zone for compliance needs.	Meets data residency requirements affordably.	Limited performance consistency.
Data Zone Provisioned	Dedicated infrastructure in a data zone for high-performance workloads.	Combines compliance with consistent performance.	More expensive than shared options.
Data Zone Batch	Batch processing within a data zone for regulated data workflows.	Ideal for compliant, large-scale processing.	Slower response times; not real-time.
Standard	Default shared deployment for general use across Azure AI Foundry.	Simple setup and broad compatibility.	May lack advanced performance or compliance features.
Regional Provisioned	Dedicated infrastructure in a specific region for localized performance.	Optimized for regional latency and control.	Higher cost and limited to regional availability.
Developer (Fine-tuned)	Lightweight deployment for testing and iterating fine-tuned models.	Fast iteration and low cost for development.	Not suitable for production-scale workloads.

Nov '25 Regional Tech Events

User Groups

• Nov 4: Capital Area .NET Users Group
• Nov 12: Azure Cleveland
• Nov 13: Akron AITP
• Nov 19: Cleveland C# User Group
• Nov 20: GLUG.NET

 

Conferences

• Nov 11-13: .NET Conf 2025

 

Converting .NET Application from Oracle to SQL Server

The SQL Server equivalent of Oracle.ManagedDataAccess.Client is either System.Data.SqlClient or Microsoft.Data.SqlClient

System.Data.SqlClient is the older built-in provider.

Microsoft.Data.SqlClient is the newer, actively maintained version with better support for .NET Core and .NET 5+.

 

Feature	Oracle.ManagedDataAccess.Client	System.Data.SqlClient / Microsoft.Data.SqlClient
Database	Oracle	SQL Server
Namespace	Oracle.ManagedDataAccess.Client	System.Data.SqlClient or Microsoft.Data.SqlClient
Connection class	OracleConnection	SqlConnection
Command class	OracleCommand	SqlCommand
Data reader class	OracleDataReader	SqlDataReader
NuGet package	Oracle.ManagedDataAccess	System.Data.SqlClient (legacy) or Microsoft.Data.SqlClient (modern)

 

How can I remove GitHub bindings from a Visual Studio 2022 Solution

To remove Git from a solution in Visual Studio 2022, effectively unbinding it from source control, follow these steps:

1. Ensure the solution is NOT open in the Visual Studio IDE.
2. Navigate to the root directory of your solution using File Explorer.
3. If you cannot see the .git folder, you need to enable the display of hidden files and folders in File Explorer. In Windows, open File Explorer, go to the "View" tab, and check "Hidden items."
4. Delete the .git folder within your solution's root directory. This folder contains all the Git repository information, including history, branches, and tags for the solution and all projects within it.
5. Visual Studio should now recognize that the Git repository is no longer present and will no longer manage it with Git source control.

Oct '25 Regional Tech Events

User Groups

• Oct 7: Ohio North Database Training
• Oct 8: Azure Cleveland
• Oct 16: Akron AITP
• Oct 16: GLUG.NET
• Oct 22: Cleveland C# User Group

 

Conferences

• Oct 18: SQL Saturday PGH

 

.NET MAUI with Blazor vs. XAML

 

What's better for mobile development with .NET Maui, Blazor or XAML?

Each has its pros and cons.  Listed below is a brief comparison of the 2 options:

Maui with Blazor: Web Tech, Shared Logic

Best for: Web developers or teams already using Blazor for web apps who want to reuse components and logic.

Pros:

- Write UI in Razor syntax (HTML + C#)

- Share components across web and mobile

- Easier onboarding for web devs

- Great for internal tools or hybrid apps

Cons:

- Slight performance overhead compared to native XAML

- Limited access to some native features (though improving)

- Smaller ecosystem for mobile-specific Blazor components

Maui with XAML: Native Feel, Rich Control

Best for: Developers with WPF, UWP, or Xamarin.Forms experience, or those wanting full control over native UI.

Pros:

- Deep integration with MAUI’s native controls

- Rich styling and layout capabilities

- More mature tooling and community support for mobile-specific features

- Better performance for complex or animation-heavy UIs

Cons:

- Steeper learning curve if you're new to XAML

- Less web-like, so not ideal if you're coming from a web dev background

Conclusion

- If you're building consumer-facing apps with polished native UI and animations: go XAML.

- If you're building internal tools, cross-platform dashboards, or want to reuse Blazor components: go Blazor.

- If you're new to mobile dev but strong in web: Blazor will feel more natural.

- If you're already deep in .NET desktop or mobile: XAML will give you more power.

Aug '25 Regional Tech Events

User Groups

• Aug 5: Ohio North Database Training
• Aug 7: Azure Cleveland
• Aug 21: GLUG.NET
• Aug 27: Cleveland C# User Group

 

Conferences

• Aug 1: Cincy Deliver
• Aug 13-15: Kansas City Developer Conference

 

Jul '25 Regional Tech Events

User Groups

• Jul 16: Akron AITP
• Jul 17: GLUG.NET
• Jul 23: Cleveland C# User Group

 

Conferences

• Aug 1: Cincy Deliver
• Aug 13-15: Kansas City Developer Conference

 

Jun '25 Tech Events

Virtual User Groups

• Jun 3: Ohio North Database Training
• Jun 5: Azure Cleveland
• Jun 19: GLUG.NET
• Jun 26: Cleveland C# User Group

 

Conferences

• Aug 1: Cincy Deliver
• Aug 13-15: Kansas City Developer Conference

 

7 Business Advantages of a Custom Copilot

Microsoft Copilot is an AI generative assistant, designed to understand users requests in every day common spoken language.

This assistant can be custom tailored for a specific business to quickly provide answers to customers. 

This eliminates the need for customers to browse a web site or use a search engine to get answers for specific products (i.e. pricing, sizes, etc.) 

Instead, customers can now ask questions like "What colors are available?" and receive direct answers.

 

This provides every business with an edge over the competition.

Here's why investing in a custom Copilot could be one of the smartest moves for your business.

 

1. Enhanced Efficiency & Productivity

A custom Copilot is designed to integrate seamlessly into your website or app.

 

2. Business Specific Expertise

A custom Copilot can be trained with your business-specific knowledge, making it an expert in your particular business domain.

This would allow customers to ask it specific questions and get specific answers, in plain everyday English

 

3. Reach More Customers

A custom copilot can offer Speech Capabilities where questions can be asked verbally and answers provided via audio. 

This would help reach visually or physically impaired customers.

 

4. Reach More International Customers

By using Language Translation, your custom Copilot can communicate with international customers in the language of their choice,

providing more reach for the foreign customer base. More Customers = More Sales.

 

5. Competitive Edge

By quickly providing answers to your customers' questions, a business can quickly gain an advantage over its competition. 

No longer do customers need to use a search engine or browse a web site for answers on pricing & availability. 

Instead, a quick question and answer with copilot will get the job done quickly leading to a better customer experience and potentially increased sales.

 

6. Increased Data Security & Compliance

Custom Copilots can be designed with specific security protocols and compliance measures that align with your business needs.

By controlling how data is processed, stored, and shared, companies can minimize risks associated with third-party AI services while ensuring compliance with regulatory requirements.

In addition, Microsoft's data policy on AI is "your data remains your data only".

 

7. Cost Savings & ROI

While a custom Copilot requires a single upfront investment in development, the long-term benefits far outweigh the costs.

It will quickly provide answers to customers without negatively impacting CSRs.

Businesses can reduce labor costs, improve service efficiency, and capitalize on AI-driven insights to boost profitability over time.

 

 

In a Nutshell…

A custom Copilot isn't just an AI tool—it's a strategic advantage. By tailoring AI to your business needs, you can drive efficiency, enhance customer experiences,

maintain security, and gain a competitive edge in your industry. In a world where technology is reshaping the way we work, a personalized AI solution could be the

key to unlocking the next level of success for your business.

Ready to explore the possibilities? Let's build a future where AI works for you, not just with you.

What's Stable Diffusion?

Stable Diffusion is a text-to-image model, a type of generative AI that creates images based on text prompts. It uses diffusion techniques and operates in a latent space to generate detailed and photorealistic images.

It’s similar to Dall-E and Midjourney but offers different advantages:

 

Strengths: Offers the most customization options, allowing users to fine-tune image generation with various parameters.

Use Cases: Ideal for tasks requiring precise control over the image generation process, such as image editing and manipulation.

Accessibility: Available as both a free and paid service, with different tiers of access.

Interface: Can be accessed through various platforms, such as DreamStudio and Azure AI Foundry.

 

To get started, you’ll need to know some of the terminology and how they relate in the context of Stable Diffusion:

• Workflow: The structured process of generating images using Stable Diffusion, including steps like prompt input, model selection, and refinement.
• LoRA (Low-Rank Adaptation): A technique for fine-tuning Stable Diffusion models efficiently without retraining the entire model.
• Checkpoint: A saved state of a trained model, often in .ckpt or .safetensors format, used for loading and continuing training or inference.
• Vector: A mathematical representation of data, often used in embeddings or latent space transformations within AI models.
• Sampler: The algorithm that determines how noise is removed during image generation, affecting the final output’s quality and style.
• Tensor: A multi-dimensional array used in deep learning to store and process data efficiently.
• Safe Tensor: A format for storing model weights that improves security and prevents malicious modifications.

 

In addition, here are resources to help you get started with Stable Diffusion:

Stable Diffusion Ultimate Guide: A comprehensive tutorial covering installation, txt2img, img2img, inpainting, upscalers, and more.

Step-by-Step Quickstart Guide:  A detailed walkthrough of Stable Diffusion’s latest release, including video creation and advanced tweaks.

Crash Course for Beginners: A full course on using Stable Diffusion, including training your own model, using Control Net, and API integration.

 

The Business Advantages of Hybrid Web and Desktop Apps with .NET MAUI and Blazor

On April 23, 2025, Rachel Kang presented "Hybrid Web and Desktop apps with .NET MAUI and Blazor" to the Cleveland C# User Group. The video can be found at https://www.youtube.com/watch?v=Eg3XTkctzoE

Although this presentation was targeted to Software developers, the technology itself offers several advantages to businesses that managers and executives need to consider.

 

Businesses need applications that are versatile, scalable, and cost-effective. Enter .NET MAUI and Blazor, a powerful combination that enables developers to build hybrid applications that seamlessly run on both web and desktop platforms. This approach offers numerous advantages to businesses looking to optimize their software solutions.

 

1. Cross-Platform Efficiency

One of the biggest advantages of using .NET MAUI and Blazor is the ability to write code once and deploy it across multiple platforms. Businesses no longer need separate teams for web and desktop development—this unified approach reduces development time and costs while ensuring consistency across different environments.

 

2. Improved User Experience

Hybrid applications built with .NET MAUI and Blazor provide a native-like experience on desktop while maintaining the flexibility of web applications. Users can enjoy fast performance, offline capabilities, and seamless integration with device features, making the application more intuitive and efficient.

 

3. Cost Savings

Developing separate applications for web and desktop can be expensive. With .NET MAUI and Blazor, businesses can leverage a single codebase, reducing development and maintenance costs. This approach also minimizes the need for extensive training, as developers can use familiar C# and .NET technologies.

 

4. Enhanced Security

Security is a top priority for businesses, and hybrid applications offer better control over data and access permissions. Unlike purely web-based applications, desktop components can store sensitive data locally, reducing exposure to online threats while still allowing cloud-based synchronization.

 

5. Seamless Integration with Existing Systems

Many businesses rely on legacy systems and third-party integrations. .NET MAUI and Blazor make it easier to connect with existing databases, APIs, and enterprise solutions, ensuring a smooth transition without disrupting operations.

 

6. Future-Proof Technology

Microsoft continues to invest in .NET MAUI and Blazor, ensuring long-term support and updates. Businesses adopting this technology can stay ahead of the curve, benefiting from continuous improvements and new features.

 

By leveraging .NET MAUI and Blazor, businesses can create powerful, flexible, and cost-effective applications that cater to both web and desktop users. Whether you're looking to streamline development, enhance security, or improve user experience, this hybrid approach is a game-changer.

Azure Tenant vs. Azure Directory

In Azure, a tenant refers to a dedicated instance of Microsoft Entra ID (formerly Azure Active Directory) that an organization receives when signing up for a Microsoft cloud service like Azure, Microsoft 365, or Dynamics 365.

 

Azure Tenant

• Identity Management: A tenant provides a centralized identity system for managing users, groups, and applications.
• Subscription Association: A tenant can own one or multiple Azure subscriptions, but each subscription belongs to only one tenant.
• Security & Access Control: Tenants enable role-based access control (RBAC) and authentication across Azure services.
• Domain Integration: Organizations can associate custom domains with their tenant for branding and authentication
• Dedicated: a Tenant is a dedicated instance of Microsoft Entra ID (formerly Azure Active Directory) that an organization receives when signing up for a Microsoft cloud service.
• Boundary: It acts as a boundary for identity management, subscriptions, and resources.
• Multiple Subscriptions:  A tenant can have multiple subscriptions, but each subscription belongs to only one tenant.

Azure Directory

• The directory is the identity service within the tenant that stores and manages users, groups, and applications.
• It enables authentication and access control across Azure services.
• The Tenant ID and Directory ID are often the same, as they refer to the same identity container.

 

Essentially, the tenant is the overarching entity, while the directory is the identity management system within it

 

For more info, visit https://learn.microsoft.com/en-us/answers/questions/1457968/help-me-to-understand-the-concepts-of-tenant-direc