Reopening this user voice item as our support for Skip/Take (Offset/Limit) was only limited to single partition queries.
The newly released .NET SDK v3 now includes support for x-partition queries using Offset/Limit. You can learn more about v3 SDK and try it and provide feedback on our github repo here.
We will also be back-porting this functionality to our .NET v2 SDK. This work will begin shortly and we anticipate it to be released in September.
Once that is released we will mark this feature as complete.
Thank you for your patience and votes.
128 votesplanned · 33 comments · Azure Active Directory » End user experiences · Flag idea as inappropriate… · Admin →
Agree, this is very confusing. Dealing with multiple Microsoft accounts and services is very messy already, would like to at least see clear information in these kinds of cases.
124 votesunplanned · 15 comments · Azure portal » Search + navigation · Flag idea as inappropriate… · Admin →
I added the same suggestion under the Automation area. This is important for any scenario where changes are happening elsewhere from portal user interaction. Views get invalidated and the user is misled about whether something is working.
Thanks for this feedback. What are the most important blades or resources to add a refresh button to?
I'm thinking any view that can be invalidated by ISE actions. For example: runbooks list, runbook summary, runbook editor. As I think about it, I wonder if this wouldn't be a general UI need, since likely most views in the portal could become obsolete. I notice a refresh button in occasional places like the "All Resources" blade, but why not have it up in the corner on all blades next to pin, min/max, close?
Thanks for this suggestion. Right now, you can see the start and end times but need to compute the duration yourself.
Thanks Beth. I think the reason this is a frustration actually relates to timestamps not providing second-level granularity. Therefore a I can't tell if a job with timestamps 9:38 - 9:39 took 10 seconds or 100. I would like to see second-level timestamps throughout, including in log entries. Maybe I should create a separate idea for that?
42 votesunder review · AdminAzure IaaS Engineering Team (Azure IaaS Engineering Team, Microsoft, Microsoft Azure) responded
We added auto-stop in the platform and we are considering the addition of auto-start as well. Please continue to vote up this item if you would like to see auto-start included with our existing auto-stop feature.
I agree that this would be nice to see as native feature. In the meantime the closest I've been able to get is by using the tags feature of the new Azure Resource Manager to set schedules per VM group. More details:
Thanks again! This is great feedback.
Thanks Noah! We can investigate selecting assets as input parameters to runbooks.
Another example would be some parameter conventions like subscription. In the case where I'm running my test in the portal, it's likely my current subscription or another I have access is what I want. So, nice to pop those into a dropdown as a quick option instead of an empty string field.