Friday, May 2, 2025

What difference between Microsoft Power BI Desktop (Optimized for Power BI Report Server - September 2024) and Microsoft Power BI Desktop and Microsoft® Power BI Report Builder

  The differences between Microsoft Power BI Desktop (Optimized for Power BI Report Server - September 2024), Microsoft Power BI Desktop, and Microsoft Power BI Report Builder lie in their purpose, functionality, and target environment. Below is a concise comparison:

1. Microsoft Power BI Desktop (Optimized for Power BI Report Server - September 2024)
  • Purpose: A specialized version of Power BI Desktop tailored for creating and publishing reports to Power BI Report Server, an on-premises reporting platform.
  • Key Features:
    • Optimized for compatibility with Power BI Report Server (September 2024 release).
    • Does not include preview features until they are generally available, ensuring stability for on-premises environments.
    • Supports interactive Power BI reports (.pbix files) and connectivity to on-premises data sources without requiring a gateway for local data.
    • Lacks some cloud-specific features (e.g., dashboards, Q&A, shared datasets, advanced AI/ML capabilities) available in the Power BI Service.
    • Can be installed side-by-side with standard Power BI Desktop.
  • Environment: On-premises, designed for organizations needing to keep data and reports within their firewall for security or regulatory reasons.
  • Limitations:
    • Does not support paginated reports (.rdl files).
    • Limited to features supported by the specific Report Server version (e.g., no export to Excel with current layout).
    • Custom security extensions may prevent direct saving to the Report Server; reports must be uploaded manually.
2. Microsoft Power BI Desktop
  • Purpose: The standard version of Power BI Desktop, designed for creating interactive reports and dashboards for the Power BI Service, a cloud-based platform.
  • Key Features:
    • Supports a broader range of features, including preview features, frequent updates, and cloud-specific capabilities like dashboards, shared datasets, Q&A, and AI-driven insights.
    • Creates .pbix files for interactive, screen-optimized reports with advanced visuals and data modeling.
    • Integrates with Microsoft Fabric and other cloud services (e.g., Power Automate, Power Apps).
    • Allows data import, transformation, and visualization from various sources using Power Query and DAX.
  • Environment: Primarily cloud-based (Power BI Service), though reports can be shared locally or published to on-premises servers with limitations.
  • Limitations:
    • Not optimized for Power BI Report Server; reports created may not be fully compatible with on-premises servers due to version differences or unsupported features.
    • Cannot create paginated reports.
3. Microsoft Power BI Report Builder
  • Purpose: A standalone tool for creating paginated reports (.rdl files) optimized for printing or exporting to formats like PDF or Excel.
  • Key Features:
    • Designed for "pixel-perfect" paginated reports with precise control over layout, ideal for printed reports or fixed-format documents.
    • Based on SQL Server Reporting Services (SSRS) technology, supporting Report Definition Language (.rdl) files.
    • Supports accessibility features (e.g., tagging headers, text box properties) and conditional formatting.
    • Can connect to Power BI datasets or other data sources via SQL Server Analysis Services.
    • Compatible with Power BI Report Server and older SSRS versions (2016, 2017, 2019).
  • Environment: Primarily used with Power BI Report Server or SSRS for on-premises deployment, though paginated reports can be published to Power BI Service with a premium capacity.
  • Limitations:
    • Lacks the interactive, exploratory features of Power BI Desktop reports.
    • Not suited for building dashboards or highly interactive visuals.
Key Differences Summary
Aspect
Power BI Desktop (Optimized for Report Server)
Power BI Desktop
Power BI Report Builder
Primary Use
Interactive reports for on-premises Report Server
Interactive reports for cloud (Power BI Service)
Paginated reports for printing/export
File Format
.pbix (interactive reports)
.pbix (interactive reports)
.rdl (paginated reports)
Environment
On-premises (Power BI Report Server)
Cloud (Power BI Service)
On-premises or cloud (premium)
Feature Set
Stable, server-compatible features
Latest features, cloud-focused
Pixel-perfect, print-focused
Preview Features
Excluded until generally available
Included
Not applicable
Data Connectivity
On-premises focus, no gateway for local data
Cloud and local with gateway
SSRS-based, dataset-focused
Interactivity
High (slicers, filters, visuals)
High (dashboards, AI)
Low (static, formatted reports)
Compatibility
Tied to specific Report Server version
Power BI Service
Report Server, SSRS, premium cloud
Which Tool to Use?
  • Use Power BI Desktop (Optimized for Report Server - September 2024) if your organization uses Power BI Report Server and needs interactive reports hosted on-premises.
  • Use Power BI Desktop for cloud-based reporting, collaboration, and access to the latest features in the Power BI Service.
  • Use Power BI Report Builder for paginated reports requiring precise formatting for printing or export, especially in on-premises environments or premium cloud workspaces.
For further details, refer to Microsoft’s official documentation on Power BI Report Server and Power BI Desktop

Monday, April 14, 2025

Azure DevOps : Add external user with access to Repos

 

How to add a user to Azure DevOps Project to ensure user has access to Repos?

For Example: When I invite a member to an Azure DevOps project, why is the invited user unable to view the repositories? The invited user has been assigned the Project Administrator role, and the permissions for the repository have been configured to allow administering labels, checking in code, and reading aloud, under user permissions in repository security settings. Could you explain why the user is still unable to view the repository?"


This issue could stem from several factors, even if the permissions seem correctly configured. Here are some possible reasons and solutions:


1. **Access Level**: Ensure the added user has a "Basic" or higher access level. Users with "Stakeholder" access cannot view or interact with repositories, even if they have permissions

2. **Repository Visibility**: Check if the repository is private or has restricted visibility. If so, ensure the user is explicitly added to the allowed users or groups

3. **Effective Permissions**: Sometimes, permissions set at a higher level (like the organization level) can override project-level permissions. Use the "Permissions" tab in the repository settings to trace the user's effective permissions and identify any conflicts

4. **Repos Service Disabled**: Verify that the "Repos" service is enabled for the project. If it's disabled, no one can access the repositories

5. **Membership in the Project**: Ensure the user is a member of the project containing the repositories. Being a project administrator doesn't automatically grant access to all repositories

6. **Browser Cache or Settings**: Occasionally, browser cache or settings can cause visibility issues. Clearing the cache or trying a different browser might hel

7. **Recent Permission Changes**: If permissions were recently updated, the user might need to refresh their client or log out and back in to see the changes

If none of these solutions resolve the issue, you might need to escalate the problem to your organization's Azure DevOps administrator to investigate further. Let me know if you'd like more detailed guidance on any of these steps!



Monday, November 25, 2024

“Book of News” for Microsoft Ignite 2024

Book of News for MS Ignite 2024 for the full set of announcements we’ve made at Microsoft Ignite 2024, and the Official Microsoft Blog  to learn more about our key announcements.

Here’s the Table of Contents:

    • 1.1. Agents 
    • 1.2. Microsoft 365 Copilot 

    • 2.1. Collaboration 
    • 2.2 Investment in AI 

    • 3.1. AI 
    • 3.2. Developer Tools 
    • 3.3. Infrastructure 
    • 3.4. Data & Analytics 
    • 3.5. Quantum 

    • 4.1. Edge 

    • 5.1. Industry 

    • 6.1. Microsoft 365 

    • 7.1. Power Platform 

    • 8.1. Security 
    • 8.2. Microsoft Purview 
    • 8.3. Security Copilot 
    • 8.4. Intune 
    • 8.5. Entra 
    • 8.6. Defender 

    • 9.1. Windows Commercial 
    • 9.2. Windows Developer