r/MicrosoftFabric • • Dec 11 '24

Community Share My current learning journey

Post image
212 Upvotes

r/MicrosoftFabric • • Mar 10 '26 Bravo

Community Share A complete set of Microsoft Fabric icons for Solution Architects

Post image
190 Upvotes

Since I couldn't find any up-to-date, usable Microsoft Fabric icons in the official repositories, I spent a few hours extracting and organizing my own set.

I’ve put together a complete pack of 304 icons, which includes:

LibraryIcons
Fabric Core + Microsoft Tools28
Fabric Artifacts82
Fabric Datasources87
Fabric Black45
Azure DevOps7
Azure Core55

I designed this collection specifically to make diagramming cleaner and easier. All icons:

  • are in lossless SVG format

  • have a consistent border style

  • have a default 60px height

  • have zero internal padding for most icons

Currently, this library is packaged specifically for draw.io, but I plan to release the standalone SVG files in the near future.

You can grab them here: https://dataguideline.com/a-complete-set-of-microsoft-fabric-icons-for-solution-architects/


r/MicrosoftFabric • • Feb 20 '25

Discussion Who else feels Fabric is terrible?

172 Upvotes

Been working on a greenfield Fabric data platform since a month now, and I’m quite disappointed. It feels like they crammed together every existing tool they could get their hands on and sugarcoated it with “experiences” marketing slang, so they can optimally overcharge you.

Infrastructure as Code? Never heard of that term.

Want to move your workitems between workspaces? Works for some, not for all.

Want to edit a DataFlow Gen2? You have to takeover ownership here, otherwise we cannot do anything on this “collaborative” platform.

Want to move away from trial capacity? Hah, have another trial!

Want to create calculated columns in a semantic model that is build on the lakehouse? Impossible, but if you create a report and read from that very same place, we’re happy to accomodate you within a semantic model.

And this is just after a few weeks.

I’m sure everything has its reason, but from a user perspective this product has been very frustrating and inconsistent to use. And that’s sad! I can really see the value of the Fabric proposition, and it would be a dream if it worked the way they market it.

Allright rant over. Maybe it’s a skill issue from my side, maybe the product is just really that bad, and probably the truth is somewhere in between. I’m curious about your experience!


r/MicrosoftFabric • • Oct 29 '24

Community Share And we shall call it Fabric!

Post image
142 Upvotes

"And we shall call it Fabric - a single, AI-powered platform!"

Does this unify our data stack?

"It is a collection of multiple services stitched together, and a combination of different pricing models."

Does it unify and integrate easily with our other Azure services?

"No, it will demand yet another migration."

Once we migrate, at least it should all work seamlessly, right?

"Error messages will be blank, you cannot access your metrics to root cause if you are throttled, and governance is all but naught."

Does it introduce new features we need?

"Nay, it lacks features you already have."

What will this cost us in production?

"No one knows."


r/MicrosoftFabric • • Jun 09 '26 Mindblown

Community Share Built a walkable 3D refinery in Microsoft Fabric using the new Rayfin SDK (Fabric Apps)

138 Upvotes

You've probably seen a few Rayfin reports and visuals floating around, here's mine!

I built a 3D refinery loosely based on the ORLEN refinery in Płock (sample data). You can walk around it, zoom into any unit, and even drive a truck through it. Video below.

At this point you can truly build any report and visualization you want. Using LLMs, you can easily create building plans, complex diagrams, custom charts, 3D models, workflows, everything that was previously unattainable with Power BI is now at your fingertips.

Anyone else gotten their hands on Rayfin yet?


r/MicrosoftFabric • • Sep 26 '24

To Microsoft with Love

137 Upvotes

Dear Microsoft,

Yes, Fabric is still a 'young' product, but to my mind there are a number of fundamental missing features and bugs with Fabric. It seems like you are continuing to rollout all sort of new features, whilst on the other hand you are not fixing for some key problems (in some cases for months now).

I have been using Fabric for the last 4 months, coming in with a rich background in Azure and Databricks. My experience thus far has been frustrating - full of bugs, missing features, and an overall uncomfortable and time-consuming processes, for simple tasks.

Some of the issues I've faced:

  1. Lack of connection between Azure DevOps Git integration and deployment pipelines. You have no idea which version you've deployed; the deployment just grabs whatever is in the workspace (which can include uncommitted changes), creating a mess. There is no way to implement a proper CI/CD for the Warhouse, as database project for Fabric are in preview, you cannot apply schema changes via schema compare, and you cannot update the warehouse via deployment pipelines because it actually drops and recreates an empty table when you add a column (what the hell?!).

  2. There's no single place to see and investigate deployment rules. You have to go into each item, in each stage , to see if it has any rules and what they are. If you didn't create the item (you're not the owner), you cannot edit or see the rules of the item! You can't change the owner of the item either. If someone created a notebook, it's theirs forever - is that really how it should work?

  3. You cannot see lakehouse shortcuts easily, only by investigating them one by one. You can't copy them between workspaces and need to create them manually.

  4. The SQL endpoint is lagging. You can get missing data, and changes/additions to the data are not reflected in real-time. There's a lag of between minutes to hours! how can you run this in prodcution like this???

  5. There are issues creating Reflexes and events that trigger pipelines. It's a hassle to create these, full of bugs, and very frustrating. I'm now facing an issue where I can't even create a Reflex - I've had to open a support ticket.

  6. You cannot change data types for columns in the warehouse or rename tables. Adding columns breaks the table in Power BI (for import mode). You cannot drop a column... This is not the way anyone would want their Datawarehouse to be in 2024, especially one that's touted as the next big thing.

  7. There's no nvarchar(max) datatype in the warehouse. Seriously?! the data i on data lake, how can you not support unlimited text size if the data is literally sitting in unlimited storage.

  8. There's no feature parity with ADF, and pipelines in Fabric and connections are personal.

  9. The price is way too high compared to Databricks.

  10. Lack of Keyvault integration. I cant use the service principal of fabric to fetch secrets. How am I supposed to use this in production?

  11. And there are many more issues beyond these, I just got tired of writing

Sorry Microsoft, I am using the product, and I don't like it.

Make me change my mind or tell me how you feel


r/MicrosoftFabric • • Oct 29 '25

Community Share OneDrive/SharePoint shortcuts announced

Post image
131 Upvotes

Out at the Power Platform Conference and they announced and live demoed OneDrive / SharePoint shortcuts and shortcut transforms

Sneak peek - so stay tuned!


r/MicrosoftFabric • • Feb 01 '25

Community Share It all goes to the same place in the end

Post image
131 Upvotes

r/MicrosoftFabric • • Apr 01 '25

Community Share Fabric Installation Disc

Post image
129 Upvotes

If you want to run all your Fabric workloads locally then look no further than the Fabric installation disc! It’s got everything you need to run all those capacity units locally so you can run data engineering, warehouse, and realtime analytics from the comfort of your home PC. Game changer


r/MicrosoftFabric • • Jun 26 '26 Bravo

Certification Finally Passed DP-700 with 830+ and over 50 mins left!

Post image
125 Upvotes

Despite the technical issues with OnVue while taking the test, it felt good to finally pass after attempting the exam twice. I'll say a big thank you to Aleksi Partanen and Will Nedham's YouTube courses. Microsoft Learn videos were also instrumental. Moreso, using Claude I was able to create a quiz tailored to my weak areas from previous exams.

Good to have PL 300, DP 600 and now DP 700.

Next - DP 800?


r/MicrosoftFabric • • Nov 03 '25

Discussion Abandoning Fabric

118 Upvotes

Having worked on Fabric extensively over the past year, we're seriously questioning the move away from Databricks. Curious to hear what your current situation is as we are planning to abandon ship due to following reasons:

  1. Saas trap: The reason we chose Fabric in the first place was that its SaaS and we thought it will take the pain of platform management away for a small team of ours - however once we started peeling the onion, we ultimately cried 🤣

  2. Docs and toolset chaos: lack of exhaustive documentation (shite at best), incompatible toolsets (hello, abandoned dbt adapter codebases) and roughly sketched muddy roadmaps. It might sound brutal but the product runs on a ticketing treadmil and lacks long term product vision

  3. Consulting wasteland: This feels deely personal. We hired local (ahem, clears throats) experts (coughing violently at the PPT deck) for a trial and ended up burning money on useless powerpoint slides and shite frameworks built to enable foundational capabilities like cicd. Feel I learnt more by doing it all on my own

  4. Feature Facepalms: Imagine building a modern data platform in 2023 where SQL Views - a concept oldern than some interns - don't even show up on lakehouse explorer. Perfectly sums up the culture shift: Optimise for shiny demos, peak buzzwords like shortcuts, but abandon the fundamentals that made data/analytics engineering reliable


r/MicrosoftFabric • • Aug 31 '26

Discussion PLEASE stop this feature

116 Upvotes

For all the Microsoft Employees in this subreddit -- I'm sorry, but I cannot find this feature useful whatsoever. Same with trying to open more than 10 workspaces at once. Please stop this... Or at least give us an option to disable this?


r/MicrosoftFabric • • Feb 19 '26 Helpful

Community Share Big news: fabric-cicd officially Microsoft supported

114 Upvotes

It is with great pleasure that we can officially announce fabric-cicd is now an official Microsoft Fabric product offering. This is a major milestone for the CI/CD story in Fabric and signals continued deep investment in this space.

Importantly, this transition does not change the open-source nature of the library — please continue to contribute and share your feature requests and ideas with the community.

As part of this next phase, ownership has moved into the product group, and u/fabshire25 has transitioned to the new team to continue driving development and innovation. Excited for what’s ahead! While my team’s core focus will shift, we’ll remain actively engaged in the community and look forward to continuing to contribute to the evolution of CI/CD in Fabric.

Announcing official support for Microsoft fabric-cicd tool | Microsoft Fabric Blog | Microsoft Fabric


r/MicrosoftFabric • • Sep 16 '26

Discussion Please give me a "Close all" button

110 Upvotes

When in Fabric view I tend to get a ton of tabs open and then it becomes a mess trying to find things. You forgot something was opened, open it another tab and then get the annoying message about there being multiple instances open of a notebook.

Would you folks at Microsoft give us a "Close all" and "Close other tabs" options so we can mass close tabs on the top of the Fabric view so we don't have to click X on every single tab. Ooops, missed the X and now it is loading that tab. It's kind of obnoxious at this point.

Thank you!


r/MicrosoftFabric • • May 23 '25

Community Share Fabric Architecture Icons Library for Excalidraw - 50 NEW Icons 😲

Thumbnail
gallery
110 Upvotes

The existing Fabric library has been updated, install it here: https://libraries.excalidraw.com/?theme=light&sort=default#mwc360-microsoft-fabric-architecture-icons

Cheers!


r/MicrosoftFabric • • Jan 23 '26 Bravo

Certification You get a voucher! You get a voucher! Everybody gets a Fabric voucher!!

109 Upvotes

I know you think I'm some sort of FabricPam AI bot, but I'm a real person who works at Microsoft who over uses emojis on our live streams and !!!!! in my teams messages and emails (and apparently post titles...)

I just got another stash of free exam DP-600 and DP-700 exam vouchers and I’d rather give them to you, my Reddit friends, than to the mysterious hordes of AI-generated survey goblins who like to keep me on my toes.

Here's the deal, fill this form out and make sure to let me know you came from Reddit. Can't hurt to drop your Reddit username so I know you are a real person. https://aka.ms/FabCert/2026

First come, first served -- limited vouchers (plenty if you apply soon!)


r/MicrosoftFabric • • Jun 11 '25

Discussion What's with the fake hype?

107 Upvotes

We recently “wrapped up” a Microsoft Fabric implementation (whatever wrapped up even means these days) in my organisation, and I’ve gotta ask: what’s the actual deal with the hype?

Every time someone points out that Fabric is missing half the features you’d expect from something this hyped—or that it's buggy as hell—the same two lines get tossed out like gospel:

  1. “Fabric is evolving”

  2. “It’s Microsoft’s biggest launch since SQL Server”

Really? SQL Server worked. You could build on it. Fabric still feels like we’re beta testing someone else’s prototype.

But apparently, voicing this is borderline heresy. At work, and even scrolling through this forum, every third comment is someone sipping the Kool-Aid, repeating how it’ll all get better. Meanwhile, we're creating smelly work arounds in the hope what we need is released as a feature next week.

Paying MS Consultants to check out our implementation doesn't work either - all they wanna do is ask us about engineering best practices (rather than tell us) and upsell co-pilot.

Is this just sunk-cost psychology at scale? Did we all roll this thing out too early and now we have to double down on pretending it's the future, because backing out would be a career risk? Or am I missing something. And if so, where exactly do I pick up this magic Fabric faith that everyone seems to have acquired?


r/MicrosoftFabric • • 26d ago

Community Share We built Weaver — an open-source data engineering framework for Microsoft Fabric

Thumbnail
gallery
106 Upvotes

Hi all,

I came to Microsoft Fabric from a Microsoft SQL Server data warehousing background, where we’d spent years developing the engineering machinery for managing large, complex data estates.

When I started working with Fabric, I found that while it had many of the underlying capabilities, the engineering experience was fragmented. Different approaches for Lakehouses, Warehouses and Power BI, and much of the tooling designed around SQL tables didn’t extend naturally to Lakehouse Files and Delta tables.

What I wanted was the same engineering discipline we’d enjoyed with traditional SQL warehouses: a single dependency graph, repeatable builds, incremental loading, fault tolerance, production-ready CI/CD, automated testing, performance optimisation and operational visibility, regardless of where the data lived.

What’s clear to me was that Fabric is great, but the adequate tooling didn’t exist.

Over the years, my colleague Mark and I built a strong SQL data engineering framework to operate a large government department’s warehouse. It’s state-of-the-art — if I may say so — but we couldn’t release it because it’s government code. However, we could create a new version tailored it to Microsoft Fabric, and make it open source for everyone..

It’s now available for free: Weaver

The idea is that Weaver makes Fabric easier to use, and safer to scale.

(Yes… I noticed afterwards we weren’t the first to do this play-on-words… but it’s already released to pypi.)

A few things already included so far:

1. Full parity between Lakehouses and Warehouses: Build and load tables or files using Python, Spark SQL and T-SQL using a consistent contract. Supports staging, change detection, incremental, fault tolerance etc.
2. A single DAG across Fabric: Connect Lakehouses, Warehouses, semantic models and reports in one dependency graph, coordinating their build, load and test workflows.
3. Enterprise Power BI: Extend semantic models and reports. Use standard TMDL annotations to apply modelling conventions, write automated DAX testing, and deploy different versions of the reports connected to different sources.
4. Fully Fabric native: No separate runtimes, no compiled code, no macros, nothing that doesn’t run on Fabric itself. All you need is pip install. Desktop CLI and Notebook have full parity so you can use either. CLI is cooler but not all government departments allow you to use desktop python.
5. UI & observability: Prepackaged Power BI report to visualise estate health, lineage graphs, ER diagrams, semantic-model bus matrices, load performance, execution timelines. It’s DirectLake so it’s “live” - skip the import and just refresh the visual to see what’s happening.
6. Performance-tuned for Fabric: Detailed performance tuning tailored to Fabric, including automatic parallel execution across the DAG, with separately configurable concurrency for Spark and T-SQL workloads, as well as other things you wish someone had done for you such as automatic background refresh for SQL endpoint.
7. Production grade CI/CD: Swap deployment targets with zero code change — just a config file swap. Deployment and orchestration can happen unattended via Notebook.
8. Developer and AI-agent workflows: A Python API and CLI with human-readable and structured JSON output, designed for rapid, repeatable engineering cycles.

One of the things I particularly wanted to validate was whether this approach could work at enterprise scale.

We’ve stress-tested Weaver with a single dependency graph containing approximately 3,000 objects and 4 billion rows, including Lakehouse and Warehouse workloads.

The results were 60 minutes full load and 15 minutes incremental on the Fabric trial capacity.

How is Weaver different from dbt?

There’s certainly overlap, especially around SQL transformations, incremental loading and testing.

The main difference is scope. dbt is primarily a data transformation framework, whereas Weaver is designed to engineer and operate an entire Microsoft Fabric estate—from Lakehouse Files and Delta tables to Warehouses, semantic models and reports—all within a single dependency graph and a common build, load, test and monitoring framework.

Weaver doesn’t introduce a new compute engine. It works with Microsoft Fabric’s native capabilities, using familiar Python, SQL and Power BI definitions.

Give it a try

It’s open source under MPL 2.0 and available on PyPI: pip install weaverstack

Website: Weaver: Making Fabric easier to use
Documentation: Developer docs
Open source code: GitHub

We’d be interested to hear how others are managing code-first data engineering on Fabric, particularly across Lakehouses, Warehouses and Power BI.

This is my first real post on Reddit. So be patient with me.

Hopefully, this is a step forward in production-level tooling for Fabric

Feedback, criticism and contributions are very welcome.


r/MicrosoftFabric • • Jun 06 '25

Discussion I don't know where Fabric is heading with all these problems, and now I'm debating if I should pursue a full-stack Fabric dev career at all

106 Upvotes

As a heavy Power BI developer & user within a large organization with significant Microsoft contracts, we were naturally excited to explore Microsoft Fabric. Given all the hype and Microsoft's strong push for PBI users, it seemed like the logical next step for our data initiatives and people like me who want to grow.

However, after diving deep into Fabric's nuances and piloting several projects, we've found ourselves increasingly dissatisfied. While Microsoft has undoubtedly developed some impressive features, our experience suggests Fabric, in its current state, struggles to deliver on its promise of being "business-user friendly" and a comprehensive solution for various personas. In fact, we feel it falls short for everyone involved.

 

Here are how Fabric worked out for some of the personas:

Business Users: They are particularly unhappy with the recommendation to avoid Dataflows. This feels like a major step backward. Data acquisition, transformation, and semantic preparation are now primarily back in the hands of highly technical individuals who need to be proficient in PySpark and orchestration optimization. The fact that a publicly available feature, touted as a selling point for business users, should be sidestepped due to cost and performance issues is a significant surprise and disappointment for them.

 

IT & Data Engineering Teams: These folks are struggling with the constant need for extensive optimization, monitoring, and "babysitting" to control CUs and manage costs. As someone who bridges the gap between IT and business, I'm personally surprised by the level of optimization required for an analytical platform. I've worked with various platforms, including Salesforce development and a bit of the traditional Azure stack, and never encountered such a demanding optimization overhead. They feel the time spent on this granular optimization isn't a worthwhile investment. We also feel scammed by rounding-up of the CU usage for some operations.

 

Financial & Billing Teams: Predictability of costs is a major concern. It's difficult to accurately forecast the cost of a specific Fabric project. Even with noticeable optimization efforts, initial examples indicate that costs can be substantial. Not even speaking about leveraging Dataflows. This lack of cost transparency and the potential for high expenditure are significant red flags.

 

Security & Compliance Teams: They are overwhelmed by the sheer number of different places where security settings can be configured. They find it challenging to determine the correct locations for setting up security and ensuring proper access monitoring. This complexity raises concerns about maintaining a robust and auditable security posture.

 

Our Current Stance:

As a result of these widespread concerns and constraints, we have indefinitely postponed our adoption of Microsoft Fabric. The challenges outweigh the perceived benefits for our organization at this time. With all the need of constant optimization, heavy py usage and inability for business users to work on Fabric anyway and still sticking to working with ready semantic models only, we feel like the migration is unjustified. Feels like we are basically back to where we were before Fabric, but just with a nice UI and more cost.

 

Looking Ahead & Seeking Advice:

This experience has me seriously re-evaluating my own career path. I've been a Power BI developer with experience in data engineering and ETL, and I was genuinely excited to grow with Fabric, even considering pursuing it independently if my organization didn't adopt it. However, seeing these real-world issues, I'm now questioning whether Fabric will truly see widespread enterprise adoption anytime soon.

 

I'm now contemplating whether to stick to Fabric career and wait for a bit, or pivot towards learning more about Azure data stack, Databricks or Snowflake.

 

Interested to hear your thoughts and experiences. Has your organization encountered similar issues with Fabric? What are your perspectives on its future adoption, and what would you recommend for someone in my position?


r/MicrosoftFabric • • Aug 04 '25

Community Share 11-hour Microsoft Fabric DP-700 Certification Course on YouTube

105 Upvotes

After more than 7 months of work and hundreds of hours of planning, recording, and editing, I finally finished my Microsoft Fabric DP-700 exam prep series and published it as one video.

The full course is 11 hours long and includes 26 episodes. Each episode teaches a specific topic from the exam using:
- Slides to explain the theory
- Hands-on demos in Fabric
- Exam-style questions to test your knowledge

Watch the full course here:
https://youtu.be/jTDSP7KBavI

Hope it helps you to get your badge! :)


r/MicrosoftFabric • • Jun 21 '25

Certification I did it!

Post image
104 Upvotes

r/MicrosoftFabric • • Jun 03 '26

Community Share Fabric Apps explained: Visualization as code in a data app dashboard

Post image
103 Upvotes

This article explains data apps, a template of Fabric Apps, which were announced yesterday at Microsoft Build. You can create an app with a frontend that uses visuals made from libraries like Vega/D3 and query the semantic model in DAX. In my testing it works quite well. Certainly the most interesting feature I've seen from Power BI or Fabric.

Notably, it's not "Vega dashboards in Fabric" .. it's a full webapp, with all the complexity (and flexibility) that comes with that. Whole new world & all...

I don't see it as a replacement for Power BI reports, but a viable alternative when you need more in terms of visualization capabilities and customization. Particularly if you have good adoption of AI tools. Anyway, hope the article is a helpful intro to the topic.


r/MicrosoftFabric • • Mar 14 '25

Data Engineering We Really Need Fabric Key Vault

101 Upvotes

Given that one of the key driving factors for Fabric Adoption for new or existing Power BI customers is the SaaS nature of the Platform, requiring little IT involvement and or Azure footprint.

Securely storing secrets is foundational to the data ingestion lifecycle, the inability to store secrets in the platform and requiring Azure Key Vault adds a potential adoption barrier to entry.

I do not see this feature in the roadmap, and that could be me not looking hard enough, is it on the radar?


r/MicrosoftFabric • • Jan 27 '25

Community Share fabric-cicd: Python Library for Microsoft Fabric CI/CD – Feedback Welcome!

101 Upvotes

A couple of weeks ago, I promised to share once my team launched fabric-cicd into the public PyPI index. 🎉 Before announcing it broadly on the Microsoft Blog (targeting next couple weeks), We'd love to get early feedback from the community here—and hopefully uncover any lurking bugs! 🐛

The Origin Story

I’m part of an internal data engineering team for Azure Data, supporting analytics and insights for the organization. We’ve been building on Microsoft Fabric since its early private preview days (~2.5–3 years ago).

One of our key pillars for success has been full CI/CD, and over time, we built our own internal deployment framework. Realizing many others were doing the same, we decided to open source it!

Our team is committed to maintaining this project, evolving it as new features/capabilities come to market. But as a team of five with “day jobs,” we’re counting on the community to help fill in gaps. 😊

What is fabric-cicd?

fabric-cicd is a code-first solution for deploying Microsoft Fabric items from a repository into a workspace. Its capabilities are intentionally simplified, with the primary goal of streamlining script-based deployments—not to create a parallel or competing product to features that will soon be available directly within Microsoft Fabric.

It is also not a replacement for Fabric Deployment Pipelines, but rather a complementary, code-first approach targeting common enterprise deployment scenarios, such as:

  • Deploying from local machine, Azure DevOps, or GitHub

  • Full control over parameters and environment-specific values

Currently, supported items include:

  • Notebooks

  • Data Pipelines

  • Semantic Models

  • Reports

  • Environments

…and more to come!

How to Get Started

  1. Install the packagepip install fabric-cicd

  2. Make sure you have Azure CLI or PowerShell AZ Connect installed and logged into (fabric-cicd uses this as it's default authentication mechanism if one isn't provided)

  3. Example usage in Python (more examples found below in docs)

    from fabric_cicd import FabricWorkspace, publish_all_items, unpublish_all_orphan_items # Sample values for FabricWorkspace parameters workspace_id = "your-workspace-id" repository_directory = "your-repository-directory" item_type_in_scope = ["Notebook", "DataPipeline", "Environment"] # Initialize the FabricWorkspace object with the required parameters target_workspace = FabricWorkspace( workspace_id=workspace_id, repository_directory=repository_directory, item_type_in_scope=item_type_in_scope, ) # Publish all items defined in item_type_in_scope publish_all_items(target_workspace) # Unpublish all items defined in item_type_in_scope not found in repository unpublish_all_orphan_items(target_workspace)

Development Status

The current version of fabric-cicd is 0.1.2 0.1.3, reflecting its early development stage. Internally, we haven’t encountered any major issues, but it’s certainly possible there are edge cases we haven’t considered or found yet.

Your feedback is crucial to help us identify these scenarios/bugs and improve the library before the broader launch!

Documentation and Feedback

For questions/discussions, please share below and I will do my best to respond to all!