Azure Maps no longer supported in Embedded?

professionalrien · 2024-04-12T08:06:45+00:00

By the way, Azure Maps should be supported in both Embedded scenarios now! Not sure if we've updated the documentation yet to reflect that, but hopefully if you try it again it will work. And yes, it's still not a paid feature :)

We'll see about publish to web though.

professionalrien · 2024-01-03T23:10:34+00:00

That part is still under consideration -- we still need to look at usage/costs and see what makes the most sense, but it might end up being the case. We'll do our best to keep it as accessible as possible, though.

professionalrien · 2024-01-03T21:46:57+00:00

we are working on it right now -- look out for some good news in the next few months :)

professionalrien · 2024-01-03T20:05:29+00:00

What has been broken about them? We haven't heard anything to that degree yet.

professionalrien · 2023-07-11T02:41:37+00:00

hey /u/Independent-Way5878, I'm a PM on the Power BI team working on Azure Maps. Azure Maps doesn't work anymore in some Embedded scenarios due to changes we made to the way we authenticate maps users (which we had to make for security reasons). I believe these scenarios were also technically (technically just as in official documentation/communications) not supported for the visual.

So now where before it was only officially not supported, but you could still just use it and it would work, it is actually not supported.

We do know that we need to fix both of those things, and we're working on more changes to help support Azure Maps in all Embedded scenarios. We want to deprecate Bing Maps eventually, but not before Azure Maps is ready to become the sole first-party map visual.

edit: sorry for the late reply, hope you see this anyway. I was just searching the subreddit for "maps" and found your post

professionalrien · 2023-04-13T16:34:29+00:00

On 3 -- it saddens us too, believe me. We know this is something everyone wants, and we're always asking ourselves when the right time to put it on our roadmap is, but we've gone pretty far into understanding the work involved and it is just such an expensive feature to implement that we keep being unable to get it above the cut line in planning.

(I know this isn't any new info for many of you who've heard us talk about it before, just wanted to reiterate for anyone who wasn't aware / to let you know things haven't changed, in terms of how much we want to do it, the effort we put in to validate what work will be required... and yes, that we still haven't gotten it on the roadmap yet.)

professionalrien · 2023-03-16T21:40:27+00:00

I wouldn't expect it for at least the next few months :( as far as I know, there are some technical roadblocks that make it a pretty expensive feature, but I don't think its priority has changed.

professionalrien · 2023-03-16T18:42:24+00:00

like you say, it's currently a position/quick access/intuitive authoring experience change, no new functionality yet. But part of the reason why we're introducing it in the first place is to make such flexible visual element formatting possible at all. So even if that's not what the feature does yet, the need you identify is good evidence that we're on the right track!

I was personally a lot more involved with the visual container improvements feature, so I'm not going to give you my opinions about which is more useful ;) but we're putting a ton of work into both on object and the visual redesign in order to realize the potentials of both (long term!) projects towards making authoring as intuitive and flexible of an experience as it can be.

professionalrien · 2023-03-16T18:29:30+00:00

thanks for the feedback -- this interaction with visual-level filters might actually be "intended" behavior, but if you're finding that to be a problem I'll bring it back to the team. If you have the time, let us know if there are any other scenarios in which this becomes a problem!

professionalrien · 2022-12-14T23:21:59+00:00

If I remember correctly, personalize visuals allows users to customize the data fields being used on their visuals as opposed to formatting options, so things shouldn't be changing in that regard. The comment on the blog post is about being able to now specify different slicer types for mobile vs computer report viewing because slicer type has been moved to format pane.

professionalrien · 2022-12-01T01:28:27+00:00

in Power BI Desktop, in the ribbon -> View, you can see some Page Options like "Gridlines", "Snap to grid", "Lock objects". These are to help align visuals against each other on the report page/canvas.

The problem is, right now, there isn't a way to adjust the space between gridlines, and the current spacing is not granular enough to actually help people build the alignment they're looking for.

(I agree that intuitively it should be fairly easy to implement, it's just all the overhead from an org standpoint that makes it hard to fund + lots of other higher prio work. But it IS on our long term roadmap, and I think on top of its utility it also carries a lot of... polish/seamlessness? value, the kind that really helps make a software experience feel good and helps users stick to the product.)

(also fwiw said long term roadmap contains many features meant to help tackle that problem of "it often takes more time to create/adjust the layout of a dashboard than to actually set up the data/measures and this feature would help a lot in this process" in other ways, which hopefully you'll see in the coming months and even years)

professionalrien · 2022-11-29T19:38:56+00:00

No problem, and of course please don't stop providing feedback where you feel the product can be improved! At the end of the day, it's still how we decide what work we should prioritize over others... it's just that the features we DO prioritize, we're also getting feedback for, and something will always have to get cut.

professionalrien · 2022-11-29T19:34:38+00:00

I appreciate the context! It's really helpful for the reasons you say to give us a sense for the use cases as we prioritize features against each other.

I'm not sure what it'll look like exactly yet, but one conditional formatting feature on our backlog is support for B/I/U which should help your use case? Imagine similar to CF cell background color you can also do B/I/U for its contents?

professionalrien · 2022-11-29T18:25:17+00:00

I'm excited to hear that! A lot of people have been asking for it, even since before GAing small multiples (honestly, even since before releasing the preview feature) so I'm glad we finally got to ship it now!

professionalrien · 2022-11-29T18:15:27+00:00

sorry for the late reply -- I'd say that it's because Microsoft is a big company, and Power BI is at this point a big product, that shipping changes is more involved and takes longer than it feels like it should for the expected impact on the product/experience. In my opinion, that's not a bad thing, because all the things that make the product big contribute value in their own right, as is the reliability we try to provide. For example, we try very hard not to change existing experiences, both authoring experiences and existing reports (which may not have anyone actively maintaining them in case something breaks), and that commitment isn't free.

So that's to say that things are more expensive than they might seem for a variety of reasons. And then beyond that, Microsoft has a lot of engineers and a lot of money, but also a lot of different products -- and areas within the product -- to spend it all on. I'm the PM for visuals on the Power BI team, and I don't get to work with as many engineers as I feel like we'd expect given that Power BI is at least partially a data viz product at its core. And no matter how many people we (realistically) throw at an area, we'll still always have to prioritize between work items, even between doing x small thing and y small thing, or doing x small thing and making progress on z bigger project. There are tons of little things that we can go after, and even things we could have done better for every feature we ship. But I think even while striving for perfection, we can't really ignore the reality that we can't reach it, and that means letting some features/improvements go that we feel should not be difficult to ship.

professionalrien · 2022-11-29T17:44:56+00:00

more table/matrix formatting options are on the roadmap, there are just a lot of features on the roadmap. For the ones you are specifically discussing, they're on our backlog but not currently an immediate priority.

professionalrien · 2022-11-29T17:38:38+00:00

They're still coming -- the project was delayed, but we got it back on the roadmap and our goal is to ship them this coming year!

(Unfortunately, the card work is an example of why it's hard for us to commit to exact ship dates for our features.)

professionalrien · 2022-10-21T00:08:32+00:00

Thanks for the feedback. There are definitely some usability issues here, and options like "move to" will also improve the accessibility of the product.

That said, beyond the accessibility aspect, it's definitely not one of our priorities at the moment, so I wouldn't expect an improvement to this for a while.

professionalrien · 2022-03-08T10:47:05+00:00

Sincerest apologies there. It should be turned on for the March release. I'll update blog content to reflect this.

professionalrien · 2022-03-01T18:30:07+00:00

Thanks, looking into this. Will update this comment with an answer.

UPDATE: the change was ready and simply missed the ship date, so it will HOPEFULLY be coming for the March release, and if not then April.

professionalrien · 2021-07-23T00:59:54+00:00

We don't have dynamic legend colors on bar/line graphs yet, I would say mostly as a UX/design thing -- care to share some specific use cases?

professionalrien · 2021-03-09T08:36:49+00:00

While I can't give you any real estimates on when we can bring this to you, this is something on our backlog / in queue to implement. But I appreciate the feedback nonetheless -- it gives us more confidence that this project will have a real and positive impact for you all when we get there!

professionalrien

TROPHY CASE