text:
[VS Code] Starting collaboration session: Could not connect to the server. HTTPS connection failed, verify there are no self-signed certificates or custom cert validation policies blocking Live Share.

Error:
Starting collaboration session: Could not connect to the server. HTTPS connection failed, verify there are no self-signed certificates or custom cert validation policies blocking Live Share.
Steps to Reproduce:
1.
2.

Version Data

extensionName
VSLS

extensionVersion
1.0.657

protocolVersion
2.2

applicationName
VSCode

applicationVersion
1.37.0

platformName
Linux

platformVersion
5.0.0-20-generic

We would need the logs to investigate further, you can use the Live Share: Export Logs command to get a zip file with logs, then attach to this issue.

logs.zip
Sorry for sending them late!

repo: MicrosoftDocs/live-share


text:
Parallel Live Share sessions

Product and Version [VS/VSCode]:
OS Version [macOS/Windows/Linux]:
Live Share Extension Version:
Target Platform or Language [e.g. Node.js]:
What were you doing when you encountered the desync?
I had 2 code windows open with a live share session active in each
How often have you encountered desyncs?
first time

Hey @blackliner , could you provide some more information about the scenario? Were you Live Share from one instance of code to another on the same machine?

Nono, it was two different sessions with two different hosts.

Oh, I see. Have you continued to see issues? Were you doing anything special (aside from having two Live Share sessions running) when it happened?
Also, just curious, why did you have two Live Share sessions running at the same time? 😊

Haha, so we were in one pair programming session, when another ongoing mob-programming session needed my help. So I moved over there. Nothing special, copy pasting from clipboard, thats it.

That's awesome that you're using Live Share so much! I think it's just a coincidence that you were in two sessions at once when you got out of sync, although I'll make a note of it in case we get more evidence that it might be at play...
We're currently looking into the sync issue, but please continue to use this thread if you continue getting out of sync or notice patterns about when it happens.

Yes, we think it is an amazing tool that helps us to work together, even when spread all over the globe. We also had situations when simultaneous coding + formatting resulted in awesome desynchs, but it was good for a laugh, and a git stash later we were up to speed again ;-)

That's good to know. I'll play around with formatting + editing and see if I can reproduce.

Hey @blackliner  , we just updated the extension with some more diagnostic capabilities. If you encounter a sync issue again, could you do me a huge favor and go through the following steps?
On both the host and the guest:

Enable the liveshare.diagnosticMode setting
Open the file that's out of sync
Run the liveshare.getCoeditingInformation command (ctrl+shift+p to open the command palette, then search for "Get co-editing information") and paste the results below

To check that messages are being sent and received, open the Output view (ctrl+shift+u) and select "Visual Studio Live Share Coediting" from the dropdown. Type a character. On the sending end, you should see output like:
[2020-12-10 23:51:25.351 ] Post message: {"messageType":"textChange","changes":[{"length":0,"newText":"a","start":400}],"changeServerVersion":12,"clientId":24,"fileName":"/src/foo.txt","time":1607644285349,"sendId":16}
On the receiving end, you should see output like:
[2020-12-10 23:51:27.713 ] Receive message: {"context":{"GuestSessionId":"31","IsOwner":"False"},"sourceId":"Coauthoring","eventId":45,"jsonContent":"{"messageType":"textChange","changes":[{"length":0,"newText":"a","start":400}],"changeServerVersion":12,"clientId":24,"fileName":"/src/foo.txt","time":1607644427514,"sendId":25}","time":1607644427713}
Are messages being sent and received?

Yes of course, I will keep it in mind and give you a heads up with the results 👍

Thank you so much 😊

Hey @blackliner , have you had any recent issues with synchronization? We've pushed out a lot of fixes over the past few months and I hope they've made the product more reliable for you.

Hey, in fact we are using live share intensively, also with multiple devs at the same time, and did not have any such issues 👍 well done, thanks for staying on it!

Excellent! I'll close this for now then. If you do hit any issues in the future, don't hesitate to let us know.

source: gharchive/issue

authors: blackliner daytonellwanger

license_type: permissive

license_source: github-api


text:
edit

[X] Content fix

Docs Build status updates of commit d346596:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Community/media/library-scenarios/index.md
:bulb:Suggestion
View
Details

Community/versioning-basics-best-practices.md
:bulb:Suggestion
View
Details

Community/media/library-scenarios/index.md

Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

Community/versioning-basics-best-practices.md

Line 77, Column 0: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: https://docs.microsoft.com/sql/relational-databases/track-changes/about-change-data-capture-sql-server?view=sql-server-2017 NOTE: This Suggestion will become a Warning on 1/29/21.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

source: gharchive/pull-request

license: MIT


text:
Clear as Mud

The statement "Defender Vulnerability Management add-on Additional capabilities for Defender for Endpoint Plan 2"  in the top table.Doesn't make sense. When you click on all of the links under that section then all of those components are included in of DFE Plan 2. What is the difference? Would be good to have a simple table that has the tick and cross per component starting with DFE P2 then map out want is added when you purchase the additional SKU.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: d4383e31-f80e-65de-3a90-9bb53b6845d2
Version Independent ID: d4383e31-f80e-65de-3a90-9bb53b6845d2
Content: Compare Microsoft Defender Vulnerability Management offerings
Content Source: microsoft-365/security/defender-vulnerability-management/defender-vulnerability-management-capabilities.md
Service: microsoft-365-security
Sub-service: mdvm
GitHub Login: @siosulli
Microsoft Alias: siosulli

@Jlouden9 Thank you for your feedback. For the features listed in the section:
Defender Vulnerability Management add-on
Additional capabilities for Defender for Endpoint Plan 2
They are only available if you install the Defender Vulnerability Management add-on on top of MDE P2. They are not in Defender for Endpoint Plan 2.
This table focuses on Defender Vulnerability Management capabilities.
Details on the Defender for Endpoint Plan can be found here:
https://learn.microsoft.com/en-us/microsoft-365/security/defender-endpoint/defender-endpoint-plan-1-2?view=o365-worldwide#compare-microsoft-endpoint-security-plans-1
I will track your feedback that table with ticks would be useful and look into it.
Thanks.


text:
Missing RSS feed for "What's new in Microsoft Defender for Office 365"

I'm unable to find an RSS feed of the following page:
https://learn.microsoft.com/en-us/microsoft-365/security/office-365-security/defender-for-office-365-whats-new?view=o365-worldwide
https://github.com/MicrosoftDocs/microsoft-365-docs/blob/public/microsoft-365/security/office-365-security/defender-for-office-365-whats-new.md
Done the following triage:

The page does not contain a link
No "rss" in page source
Previous versions of the pages on Github do not have the link
Tried to manually create the RSS URL by copying the format of others e.g. https://aka.ms/mdo/rss
Used RSS checker websites

Please can Microsoft investigate and resolve. Thank you

@itsgaryk, I don't think that article ever had an RSS feed.

authors: chrisda itsgaryk


text:
Typo - "user principle name"

Please change "user principle name" to "user principal name"
[Enter feedback here]

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 115cfe0b-c8b5-193d-19da-a6f9c03fdfc0
Version Independent ID: 4a90cb9e-ce2a-a3f6-4b67-32f45c975323
Content: Manage holds in Advanced eDiscovery - Microsoft 365 Compliance
Content Source: microsoft-365/compliance/managing-holds.md
Service: o365-seccomp
GitHub Login: @markjjo
Microsoft Alias: markjjo

@sujitnaray - Thank you for pointing this out.
PR #2076 has been created to fix and close this issue once the PR is merged.
Thank you and we appreciate your contribution to make the docs better!

PR merged

authors: markjjo mypil sujitnaray


text:
Update advanced-hunting-devicelogonevents-table.md

Made changes to the remote IP description as it is the IP address the connection is coming from

Issue#https://github.com/MicrosoftDocs/microsoft-365-docs/issues/7378

@schmurky Please merge this PR. Thanks

@yogkumgit please update the base branch and resubmit. @schmurky please validate before i merge. Thanks!

@msbemba

Hello I am checking with the PM and will give feedback soon.

@yogkumgit   @schmurky
I have updated the base branch

I'm still waiting for feedback, sorry

@schmurky Awaiting your kind response. Thanks

Hi, Yogesh,
Hopefully I get an answer tomorrow, I followed up.
From: Yogesh Kumar @.>
Sent: Tuesday, March 15, 2022 2:24 PM
To: MicrosoftDocs/microsoft-365-docs @.>
Cc: Macky Cruz @.>; Mention @.>
Subject: Re: [MicrosoftDocs/microsoft-365-docs] Update advanced-hunting-devicelogonevents-table.md (PR #7399)
@schmurkyhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fschmurky&data=04|01|Macky.Cruz%40microsoft.com|26907c8efbf44c7c8aeb08da064c68d1|72f988bf86f141af91ab2d7cd011db47|1|0|637829222530372032|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=gZqjAZPVSIcuEjWkK1WmQtTH7gG5PIG5dxZkgWrdpro%3D&reserved=0 Awaiting your kind response. Thanks

Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fmicrosoft-365-docs%2Fpull%2F7399%23issuecomment-1067608641&data=04|01|Macky.Cruz%40microsoft.com|26907c8efbf44c7c8aeb08da064c68d1|72f988bf86f141af91ab2d7cd011db47|1|0|637829222530372032|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=DcR%2BdBx%2FHswcVuw%2FIM1o1bcChK%2BAwAxLXO7uYoQSDx0%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAP2G3GYSKTI3K72KHZY4TWTVAAUINANCNFSM5L65YQ7A&data=04|01|Macky.Cruz%40microsoft.com|26907c8efbf44c7c8aeb08da064c68d1|72f988bf86f141af91ab2d7cd011db47|1|0|637829222530372032|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=DJ%2BY2DdmeStWRraS6j37ybHAW95vgIVTFXOvaPncOKs%3D&reserved=0.
Triage notifications on the go with GitHub Mobile for iOShttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04|01|Macky.Cruz%40microsoft.com|26907c8efbf44c7c8aeb08da064c68d1|72f988bf86f141af91ab2d7cd011db47|1|0|637829222530372032|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=LMT8HHIQR8HgWgAuuhXbpbLUXif0DtOncu5Be4wrp5o%3D&reserved=0 or Androidhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04|01|Macky.Cruz%40microsoft.com|26907c8efbf44c7c8aeb08da064c68d1|72f988bf86f141af91ab2d7cd011db47|1|0|637829222530372032|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=g91iHFh4LEpo%2FDcmTm1yMZXbhMNZK%2Bbq%2FU8KOutSKWA%3D&reserved=0.
You are receiving this because you were mentioned.Message ID: @.***>

@schmurky Please update, Thanks

@schmurky I have made the requested changes.

authors: DulceMontemayor msbemba schmurky yogkumgit


text:
Update README.md

Purpose

...

Does this introduce a breaking change?

[ ] Yes
[ ] No

Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test

Get the code

git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install

Test the code

What to Check
Verify that the following are valid

...

Other Information

This is a copy or fork.

repo: MicrosoftDocs/mslearn-cosmos-java-sql


text:
Bugfix/home page typo

Fix the typo on the home page

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: ckabates sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

authors: ckabates msftclas


text:
How to get the subEntityId from deep link on mobile teams client

Hi all,
I am trying to get the subEntityId from deep link for the teams app, the teams app is built by spfx framework. It works fine on both web and desktop teams client, however when it comes on the mobile client, it didn't work anymore.
This is the way I get the subEntityId, I am using the teams javaScript client SDK
microsoftTeams.getContext((c) => {         this.setState({ state1: c, location: c.subEntityId });       });
I have also tried the deep link using https and msteams protocol, it still not working.
https://teams.microsoft.com/l/entity/d4bec247-9ece-404a-8f4a-16f275def087/tasklist123?webUrl=https://tasklist.example.com/123/456&context={"subEntityId": "detail"}
msteams://teams.microsoft.com/l/entity/d4bec247-9ece-404a-8f4a-16f275def087/tasklist123?webUrl=https://tasklist.example.com/123/456&context={%22subEntityId%22:%20%22detail%22}
May I know is deep link for subEntityId is not supported on mobile client? If not, any road map we can have this features?
Thanks all for your help

Hello,
We are closing this issue as we have already got your issue link and we are looking into it.
Thanks.

repo: MicrosoftDocs/msteams-docs


text:
[Rendering] Microsoft Teams does not post back the Data property of Action.Submit if it is a string

Copied bug from: https://github.com/microsoft/AdaptiveCards/issues/8064
Details from original post:
Target Platforms
Other
SDK Version
REST API 1.3
Application Name
Microsoft Teams
Problem Description
If I send a Card to Teams with an Action.Submit's Data set to a string, Teams does not send it back in the value property of the message event.
If the Data is an object, then Teams sends it back.
According to the documentation, both strings and objects can be used (https://adaptivecards.io/explorer/Action.Submit.html)
This will produce an empty value field in the message event:
{ ...
  "content": {
    "type": "AdaptiveCard",
    ...
    "body": [ ... ]
    "actions": [
      {
        "type": "Action.Submit",
        "title": "Title",
        "data": "something"
      }
    ]
  }
}

This will produce "value": { "response": "something" } in the message event:
{ ...
  "content": {
    "type": "AdaptiveCard",
    ...
    "body": [ ... ]
    "actions": [
      {
        "type": "Action.Submit",
        "title": "Title",
        "data": {
          "response": "something"
        }
      }
    ]
  }
}

Screenshots
No response
Card JSON
{
  "type": "AdaptiveCard",
  "$schema": "https://adaptivecards.io/schemas/adaptive-card.json",
  "version": "1.3",
  "body": [
    {
      "type": "TextBlock",
      "text": "Question",
      "size": "Medium",
      "wrap": true
    }
  ],
  "actions": [
    {
      "type": "Action.Submit",
      "title": "Title",
      "data": "something"
    }
  ]
}

Sample Code Language
No response
Sample Code
No response---
Document Details
⚠ Do not edit this section.It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 3fb4394d-25b1-8752-3996-fe3a2934732d
Version Independent ID: 6d391381-89d0-117c-27cc-00043bd26a36
Content: Cards reference - Teams
Content Source: msteams-platform/task-modules-and-cards/cards/cards-reference.md
Product: msteams
GitHub Login: @surbhigupta12
Microsoft Alias: surbhigupta12

@gildas - Thanks for reporting your issue. We will test this with Action.Submit's Data set with string value and update you soon.

@gildas - We are able to repro this issue, we have raised a bug for the same. We will keep you posted if there are any updates.

Hello @@gildas - Sorry for delay in response.
We are actively checking with engineering team for the bug fixes and let you know if any.


text:
1065027 sso support for bots

Created new file auth-aad-sso-bots.md also added images. Requesting review.

Docs Build status updates of commit 0035707:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/bots/how-to/authentication/auth-aad-sso-bots.md
:warning:Warning
View
Details

msteams-platform/assets/images/bots/botframework-service-diagram.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots- VuSSOBotConnection -settings.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots- VuSSOBotHandle2-Settings.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-consent-dialogbox.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-sample-payload.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-signintokenExchange-diagram.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-sso-diagram.png
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/authentication/auth-aad-sso-bots.md

Line 13, Column 0: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/bots/how-to/authentication/auth-flow-bot' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 20, Column 0: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/bots/how-to/authentication/add-authentication?tabs=dotnet%2Cdotnet-sample' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 36, Column 0: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/tabs/how-to/authentication/auth-aad-sso' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 63, Column 0: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/tabs/how-to/authentication/auth-aad-sso' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 67, Column 0: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/tabs/how-to/authentication/auth-aad-sso' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 67, Column 0: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/tabs/how-to/authentication/auth-aad-sso#1-create-your-azure-active-directory-azure-ad-application' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 73, Column 0: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/tabs/how-to/authentication/auth-aad-sso#2-update-your-microsoft-teams-application-manifest' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 82, Column 0: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/dotnet/api/microsoft.bot.schema.oauthcard?view=botbuilder-dotnet-stable' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 140, Column 0: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/dotnet/api/microsoft.bot.schema.tokenexchangeinvokerequest?view=botbuilder-dotnet-stable' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 82, Column 0: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: https://docs.microsoft.com/en-us/dotnet/api/microsoft.bot.schema.oauthcard?view=botbuilder-dotnet-stable NOTE: This Suggestion will become a Warning on 1/29/21.
Line 96, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning on 1/29/21.
Line 140, Column 0: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: https://docs.microsoft.com/en-us/dotnet/api/microsoft.bot.schema.tokenexchangeinvokerequest?view=botbuilder-dotnet-stable NOTE: This Suggestion will become a Warning on 1/29/21.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 236b417:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/authentication/auth-aad-sso-bots.md
:bulb:Suggestion
View
Details

msteams-platform/assets/images/bots/botframework-service-diagram.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots- VuSSOBotConnection -settings.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots- VuSSOBotHandle2-Settings.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-consent-dialogbox.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-sample-payload.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-signintokenExchange-diagram.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-sso-diagram.png
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/authentication/auth-aad-sso-bots.md

Line 82, Column 0: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: https://docs.microsoft.com/dotnet/api/microsoft.bot.schema.oauthcard?view=botbuilder-dotnet-stable NOTE: This Suggestion will become a Warning on 1/29/21.
Line 111, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning on 1/29/21.
Line 142, Column 0: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: https://docs.microsoft.com/dotnet/api/microsoft.bot.schema.tokenexchangeinvokerequest?view=botbuilder-dotnet-stable NOTE: This Suggestion will become a Warning on 1/29/21.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 287c090:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/authentication/auth-aad-sso-bots.md
:bulb:Suggestion
View
Details

msteams-platform/assets/images/bots/botframework-service-diagram.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots- VuSSOBotConnection -settings.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots- VuSSOBotHandle2-Settings.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-consent-dialogbox.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-sample-payload.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-signintokenExchange-diagram.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-sso-diagram.png
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/authentication/auth-aad-sso-bots.md

Line 82, Column 0: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: https://docs.microsoft.com/dotnet/api/microsoft.bot.schema.oauthcard?view=botbuilder-dotnet-stable NOTE: This Suggestion will become a Warning on 1/29/21.
Line 111, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning on 1/29/21.
Line 142, Column 0: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: https://docs.microsoft.com/dotnet/api/microsoft.bot.schema.tokenexchangeinvokerequest?view=botbuilder-dotnet-stable NOTE: This Suggestion will become a Warning on 1/29/21.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 6a495c7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/authentication/auth-aad-sso-bots.md
:bulb:Suggestion
View
Details

msteams-platform/assets/images/bots/botframework-service-diagram.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots- VuSSOBotConnection -settings.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots- VuSSOBotHandle2-Settings.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-consent-dialogbox.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-sample-payload.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-signintokenExchange-diagram.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-sso-diagram.png
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/authentication/auth-aad-sso-bots.md

Line 82, Column 0: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: https://docs.microsoft.com/dotnet/api/microsoft.bot.schema.oauthcard?view=botbuilder-dotnet-stable NOTE: This Suggestion will become a Warning on 1/29/21.
Line 110, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning on 1/29/21.
Line 139, Column 0: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: https://docs.microsoft.com/dotnet/api/microsoft.bot.schema.tokenexchangeinvokerequest?view=botbuilder-dotnet-stable NOTE: This Suggestion will become a Warning on 1/29/21.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 353df71:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/authentication/auth-aad-sso-bots.md
:bulb:Suggestion
View
Details

msteams-platform/assets/images/bots/botframework-service-diagram.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots- VuSSOBotConnection -settings.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots- VuSSOBotHandle2-Settings.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-consent-dialogbox.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-sample-payload.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-signintokenExchange-diagram.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-sso-diagram.png
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/authentication/auth-aad-sso-bots.md

Line 82, Column 0: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: https://docs.microsoft.com/dotnet/api/microsoft.bot.schema.oauthcard?view=botbuilder-dotnet-stable NOTE: This Suggestion will become a Warning on 1/29/21.
Line 109, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning on 1/29/21.
Line 138, Column 0: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: https://docs.microsoft.com/dotnet/api/microsoft.bot.schema.tokenexchangeinvokerequest?view=botbuilder-dotnet-stable NOTE: This Suggestion will become a Warning on 1/29/21.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit b20439d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/authentication/auth-aad-sso-bots.md
:bulb:Suggestion
View
Details

msteams-platform/assets/images/bots/botframework-service-diagram.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots- VuSSOBotConnection -settings.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots- VuSSOBotHandle2-Settings.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-consent-dialogbox.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-sample-payload.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-signintokenExchange-diagram.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-sso-diagram.png
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/authentication/auth-aad-sso-bots.md

Line 82, Column 0: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: https://docs.microsoft.com/dotnet/api/microsoft.bot.schema.oauthcard?view=botbuilder-dotnet-stable NOTE: This Suggestion will become a Warning on 1/29/21.
Line 109, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning on 1/29/21.
Line 138, Column 0: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: https://docs.microsoft.com/dotnet/api/microsoft.bot.schema.tokenexchangeinvokerequest?view=botbuilder-dotnet-stable NOTE: This Suggestion will become a Warning on 1/29/21.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 8b1a84c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/authentication/auth-aad-sso-bots.md
:bulb:Suggestion
View
Details

msteams-platform/assets/images/bots/botframework-service-diagram.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots- VuSSOBotConnection -settings.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots- VuSSOBotHandle2-Settings.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-consent-dialogbox.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-sample-payload.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-signintokenExchange-diagram.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-sso-diagram.png
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/authentication/auth-aad-sso-bots.md

Line 82, Column 0: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: https://docs.microsoft.com/dotnet/api/microsoft.bot.schema.oauthcard?view=botbuilder-dotnet-stable NOTE: This Suggestion will become a Warning on 1/29/21.
Line 109, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning on 1/29/21.
Line 138, Column 0: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: https://docs.microsoft.com/dotnet/api/microsoft.bot.schema.tokenexchangeinvokerequest?view=botbuilder-dotnet-stable NOTE: This Suggestion will become a Warning on 1/29/21.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 16de299:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/authentication/auth-aad-sso-bots.md
:bulb:Suggestion
View
Details

msteams-platform/assets/images/bots/botframework-service-diagram.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots- VuSSOBotConnection -settings.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots- VuSSOBotHandle2-Settings.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-consent-dialogbox.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-sample-payload.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-signintokenExchange-diagram.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-sso-diagram.png
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/authentication/auth-aad-sso-bots.md

Line 82, Column 0: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: https://docs.microsoft.com/dotnet/api/microsoft.bot.schema.oauthcard?view=botbuilder-dotnet-stable NOTE: This Suggestion will become a Warning on 1/29/21.
Line 109, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning on 1/29/21.
Line 138, Column 0: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: https://docs.microsoft.com/dotnet/api/microsoft.bot.schema.tokenexchangeinvokerequest?view=botbuilder-dotnet-stable NOTE: This Suggestion will become a Warning on 1/29/21.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 5be3fc6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/authentication/auth-aad-sso-bots.md
:bulb:Suggestion
View
Details

msteams-platform/assets/images/bots/botframework-service-diagram.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots- VuSSOBotConnection -settings.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots- VuSSOBotHandle2-Settings.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-consent-dialogbox.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-sample-payload.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-signintokenExchange-diagram.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-sso-diagram.png
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/authentication/auth-aad-sso-bots.md

Line 82, Column 0: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: https://docs.microsoft.com/dotnet/api/microsoft.bot.schema.oauthcard?view=botbuilder-dotnet-stable NOTE: This Suggestion will become a Warning on 1/29/21.
Line 109, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning on 1/29/21.
Line 140, Column 0: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: https://docs.microsoft.com/dotnet/api/microsoft.bot.schema.tokenexchangeinvokerequest?view=botbuilder-dotnet-stable NOTE: This Suggestion will become a Warning on 1/29/21.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit e1edd0e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/authentication/auth-aad-sso-bots.md
:bulb:Suggestion
View
Details

msteams-platform/assets/images/bots/botframework-service-diagram.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots- VuSSOBotConnection -settings.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots- VuSSOBotHandle2-Settings.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-consent-dialogbox.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-sample-payload.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-signintokenExchange-diagram.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-sso-diagram.png
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/authentication/auth-aad-sso-bots.md

Line 82, Column 0: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: https://docs.microsoft.com/dotnet/api/microsoft.bot.schema.oauthcard?view=botbuilder-dotnet-stable NOTE: This Suggestion will become a Warning on 1/29/21.
Line 144, Column 0: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: https://docs.microsoft.com/dotnet/api/microsoft.bot.schema.tokenexchangeinvokerequest?view=botbuilder-dotnet-stable NOTE: This Suggestion will become a Warning on 1/29/21.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 756e2d7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/authentication/auth-aad-sso-bots.md
:bulb:Suggestion
View
Details

msteams-platform/assets/images/bots/botframework-service-diagram.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots- VuSSOBotConnection -settings.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots- VuSSOBotHandle2-Settings.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-consent-dialogbox.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-sample-payload.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-signintokenExchange-diagram.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-sso-diagram.png
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/authentication/auth-aad-sso-bots.md

Line 83, Column 0: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: https://docs.microsoft.com/dotnet/api/microsoft.bot.schema.oauthcard?view=botbuilder-dotnet-stable NOTE: This Suggestion will become a Warning on 1/29/21.
Line 145, Column 0: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: https://docs.microsoft.com/dotnet/api/microsoft.bot.schema.tokenexchangeinvokerequest?view=botbuilder-dotnet-stable NOTE: This Suggestion will become a Warning on 1/29/21.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 1ac5218:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/authentication/auth-aad-sso-bots.md
:bulb:Suggestion
View
Details

msteams-platform/assets/images/bots/botframework-service-diagram.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots- VuSSOBotConnection -settings.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots- VuSSOBotHandle2-Settings.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-consent-dialogbox.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-sample-payload.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-signintokenExchange-diagram.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-sso-diagram.png
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/authentication/auth-aad-sso-bots.md

Line 85, Column 1: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: https://docs.microsoft.com/dotnet/api/microsoft.bot.schema.oauthcard?view=botbuilder-dotnet-stable NOTE: This Suggestion will become a Warning on 1/29/21.
Line 147, Column 1: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: https://docs.microsoft.com/dotnet/api/microsoft.bot.schema.tokenexchangeinvokerequest?view=botbuilder-dotnet-stable NOTE: This Suggestion will become a Warning on 1/29/21.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit af3ad61:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/bots/how-to/authentication/auth-aad-sso-bots.md
:warning:Warning
View
Details

msteams-platform/assets/images/bots/botframework-service-diagram.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-consent-dialogbox.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-sample-payload.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-signintokenExchange-diagram.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-sso-diagram.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-vuSSOBotConnection-settings.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-vuSSOBotHandle2-settings.png
:white_check_mark:Succeeded
View

msteams-platform/tabs/how-to/authentication/auth-aad-sso.md
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/authentication/auth-aad-sso-bots.md

Line 9, Column 342: [Warning-file-not-found] Invalid file link: '../../../tabs/how-to/authentication/auth-aad-sso'.
Line 58, Column 1: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: https://docs.microsoft.com/dotnet/api/microsoft.bot.schema.oauthcard?view=botbuilder-dotnet-stable
Line 119, Column 1: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: https://docs.microsoft.com/dotnet/api/microsoft.bot.schema.tokenexchangeinvokerequest?view=botbuilder-dotnet-stable

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 1bcff66:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/bots/botframework-service-diagram.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-consent-dialogbox.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-sample-payload.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-signintokenExchange-diagram.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-sso-diagram.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-vuSSOBotConnection-settings.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-vuSSOBotHandle2-settings.png
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/authentication/auth-aad-sso-bots.md
:white_check_mark:Succeeded
View

msteams-platform/tabs/how-to/authentication/auth-aad-sso.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 75eb94b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/botframework-service-diagram.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-consent-dialogbox.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-sample-payload.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-signintokenExchange-diagram.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-sso-diagram.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-vuSSOBotConnection-settings.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-vuSSOBotHandle2-settings.png
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/authentication/auth-aad-sso-bots.md
:white_check_mark:Succeeded
View

msteams-platform/tabs/how-to/authentication/auth-aad-sso.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit a66c93c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/botframework-service-diagram.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-consent-dialogbox.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-sample-payload.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-signintokenExchange-diagram.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-sso-diagram.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-vuSSOBotConnection-settings.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-vuSSOBotHandle2-settings.png
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/authentication/auth-aad-sso-bots.md
:white_check_mark:Succeeded
View

msteams-platform/tabs/how-to/authentication/auth-aad-sso.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit f01895f:
:clock10: Pending: waiting for processors (24 builds ahead of you)
:warning: Docs Build is busy, currently there are 24 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit f01895f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/botframework-service-diagram.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-consent-dialogbox.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-sample-payload.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-signintokenExchange-diagram.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-sso-diagram.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-vuSSOBotConnection-settings.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/bots-vuSSOBotHandle2-settings.png
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/authentication/auth-aad-sso-bots.md
:white_check_mark:Succeeded
View

msteams-platform/tabs/how-to/authentication/auth-aad-sso.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


text:
Clarify whatif and confirm behavior

closes https://github.com/MicrosoftDocs/office-docs-powershell/issues/10962

@JohanFreelancer9

@isrumnon Please comment. Thanks

@pbafna03 Will be looking after this area going forward

@tseward and @isrumnon Please let me know how to proceed with this PR. Thanks

@ruchiagrawal9221 can best comment on this as this is a Policy Grant cmdlet.

@ruchiagrawal9221 Please help.

@yogkumgit  Agree with @tseward .. feature team should track the bugs separately.

@get-itips

@tseward what is expected?

Then, closing.

repo: MicrosoftDocs/office-docs-powershell


text:
Update exchange-online-powershell-v2.md

Standardized 'Note' sections and added specific disambiguation for 'Basic authentication'.

Docs Build status updates of commit 6dcd857:
:clock10: Full build: the average full build time is 12 min(s) 3 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 6dcd857:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/docs-conceptual/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 636e3df:
:clock10: Full build: the average full build time is 12 min(s) 3 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 636e3df:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/docs-conceptual/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit f45c1dd:
:clock10: Full build: the average full build time is 12 min(s) 3 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit f45c1dd:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/docs-conceptual/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 239a705:
:clock10: Full build: the average full build time is 12 min(s) 3 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 239a705:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/docs-conceptual/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 08fd0cc:
:clock10: Full build: the average full build time is 12 min(s) 3 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 08fd0cc:
:warning: Validation status: warnings

File
Status
Preview URL
Details

:warning:Warning

Details

exchange/docs-conceptual/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2.md
:white_check_mark:Succeeded
View (exchange-ps)

[Warning] Failed to get the validation ruleset and validation was not completed. This happens when there's an issue with the service and continuing to retry the call could cause build delays. You might have content issues that were not reported. To retry validation, close and re-open your PR, or rebuild your branch via Docs Portal (requires admin permissions). If you need admin help or if you continue to see this message, file an issue via https://SiteHelp.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


text:
Expanding descriptions

Closes https://github.com/MicrosoftDocs/office-docs-powershell/issues/7789

Docs Build status updates of commit da95f0d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsTeamsFeedbackPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Grant-CsTeamsFeedbackPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsTeamsFeedbackPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@Kateyanne Please merge this PR. Thanks

Docs Build status updates of commit cda75f0:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsTeamsFeedbackPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Grant-CsTeamsFeedbackPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsTeamsFeedbackPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 3c1ffcf:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsTeamsFeedbackPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Grant-CsTeamsFeedbackPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsTeamsFeedbackPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 725e63b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsTeamsFeedbackPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Grant-CsTeamsFeedbackPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsTeamsFeedbackPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


text:
Cannot send Feedback at ms-docs website, missing action "tesseract OCR" in PowerAutomate

Cannot enter Feedback at the webspage
https://docs.microsoft.com/en-us/power-automate/desktop-flows/actions-reference/ocr?source=docs
even after login with my Office 365 account. So I'm posting here.
I wanted to create a little Fow for OCR over PDF files in PowerAutomate which I can start manually for scanned PDF files in OneDrive. I see some tutorials using Tesseract OCR Engine for this task, e.g.
https://www.flexmind.co/blog/how-to-use-ocr-in-power-automate-desktop/
but TesseractOCR seems to be removed from Powerautomate Actions.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 81d0345a-3fab-2adc-c7cc-c4d2b03fe0d2
Version Independent ID: c50b23b6-616c-2962-b87f-7593e7c97f4b
Content: OCR | Microsoft Docs - Power Automate
Content Source: articles/desktop-flows/actions-reference/ocr.md
Service: power-automate
GitHub Login: @mariosleon
Microsoft Alias: marleon

Hello @bauinformatiker thank you for using Power Automate Desktop. Please note, that you may find responses to your questions in the Power Automate community where technical experts can respond to such technical questions.

authors: bauinformatiker mariosleon

repo: MicrosoftDocs/power-automate-docs


text:
Outdated, no option to view Power Automate Desktop Flows.

[Enter feedback here]

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: e7b5964c-b2b0-7487-3bd1-ef03b5621cb8
Version Independent ID: 3bce966f-4d3a-f46d-b2f9-aa4a43002e61
Content: View analytics for Power Automate desktop flows - Power Platform
Content Source: power-platform/admin/analytics-ui-flow.md
Service: power-platform
Sub-service: admin
GitHub Login: @StephenRauchPM
Microsoft Alias: stephenrauch

Thanks for your comment, @russxi. This issue has been assigned to the doc author for review.

authors: bishalgoswami russxi

repo: MicrosoftDocs/power-platform


text:
Power Platform Admin Planning

Hi Team,
I have imported Power Platform Administration Planning solution successfully and imported the sample admin task excel data as well in the Admin Tasks App. But when i try to open Power Platform Administration Planning and provide the environment URL of COE toolkit in Org URL screen, am getting the below error after the import.
Error
pcat_admintasks
Microsoft SQL: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
Could you please help us on this issue. please

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 42fc4c59-a28b-803c-5415-6299814abaa5
Version Independent ID: 42fc4c59-a28b-803c-5415-6299814abaa5
Content: Set up the Power Platform administration planning component - Power Platform
Content Source: power-platform/guidance/coe/setup-admin-tasks-component.md
Service: power-platform
Sub-service: guidance
GitHub Login: @stjeffer
Microsoft Alias: stjeffer

Thanks for your comment, @lokeshkscb. This issue has been assigned to the doc author for review.

Please check that the URL is correct, the error is stating the connection can't be created because it can't be found - we often see this when the link is copied with whitespace.

authors: bishalgoswami lokeshkscb stjeffer


text:
pac canvas not available

Hi
There is no mention of how do we get this preview or the preview version of CLI. If I used pac install latest it is not giving me the Canvas actions. Would be great, if the docs can be updated on which version (public preview) this is available and how to get that version as well.
Thank You

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 0a0e3024-713b-e281-1417-21106fda3045
Version Independent ID: 177d4ac9-7856-cbea-dc61-a7d11a909273
Content: Microsoft Power Platform CLI - Power Apps
Content Source: powerapps-docs/developer/data-platform/powerapps-cli.md
Service: powerapps
GitHub Login: @Nkrb
Microsoft Alias: nabuthuk

I guess this issue is resolved, i faced the same issue yesterday and it shows up now

@karankhosla12 it didn't worked for me.. I just tried to uninstall fully and installed.. no luck..

Hi @anskanth ,
Until it will be available, you could use the Power Platform VSCode Extension (https://marketplace.visualstudio.com/items?itemName=microsoft-IsvExpTools.powerplatform-vscode)
There you get the pac version 1.6.7. having the canvas options.

Thanks @brasov2de . I saw that.. but my problem is, I'm trying to use this in an azure build pipelines and infact trying to follow your blog  and tweak it slightly to get my canvas app extracted and commited in to Git. :).
Having it part of VSCode extension might not work for me. Surprised to see why the preview nuget package is not yet published. I looked in to the extension logic and apparently it is pulling the version from some private repository of MS, not sure why it has to be so private whilst it is part of extension.

@anskanth There is a newer version released. You should be able to see the canvas commands. Closing the issue. If  you need further help, please reopen or create a new issue.

repo: MicrosoftDocs/powerapps-docs


text:
PBI Embedded doesn't support Paginated Reports

This page refers to the PBI Embedded "A" SKUs but paginated reports aren't supported in Embedded as per internal Teams discussion with PBICAT team.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 09cf6129-9d7f-0e47-75f3-89f5df01c5e9
Version Independent ID: a1d90b2d-0e8b-da1f-fa30-a3294a98dc25
Content: Paginated reports in Power BI: FAQ (Preview) - Power BI
Content Source: powerbi-docs/paginated-reports-faq.md
Service: powerbi
Sub-service: report-builder
GitHub Login: @maggiesMSFT
Microsoft Alias: maggies

Thanks for your comment, @stevejmorgan. This issue has been assigned to the doc author for review.

Hi @stevejmorgan -- thanks for your question!
The article says you can use “paginated reports on P1 – P3 SKUs for public preview. You may also use it for test/dev scenarios with A4 – A6 SKUs,” and it says you can’t use PBI embedded at all. So I'm not sure what you're asking.
Thanks!

Hi Maggie
My understanding that the A SKUs are PowerBI Embedded but I've been told by the PBICAT team that paginated reports can't be used with any flavour of Embedded.
Steve

authors: maggiesMSFT mgblythe stevejmorgan

repo: MicrosoftDocs/powerbi-docs


text:
Not working with Canada Central P1 capacity

I went through support and they confirmed this doesn't work for Canada Central. Please add support :)

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 246f0cce-9c53-3bea-15df-0fb7c8520f12
Version Independent ID: aefc566c-9abf-1e4f-6d38-18a1e192fa23
Content: Large models in Power BI Premium (preview) - Power BI
Content Source: powerbi-docs/service-premium-large-models.md
Service: powerbi
Sub-service: powerbi-admin
GitHub Login: @davidiseminger
Microsoft Alias: davidi

Thanks for your comment, @ryanscott14. I'm familiar with that support request, and we'll update the doc to be clearer.
Meanwhile, since this is product feedback rather than documentation feedback – you can submit product feedback or feature ideas by going to https://ideas.powerbi.com. You can also engage with the Power BI engineering team by being active in the Power BI Community, found at https://community.powerbi.com.


text:
R scripts is now supported in Personal gateway ,please update Document

R scripts is now supported in Personal gateway ,please update Document

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: ea871f0a-018e-0335-7261-f9d9d2232e36
Version Independent ID: 345a024a-5964-0979-494f-6f7196a3c929
Content: On-premises data gateway (personal mode) - Power BI
Content Source: powerbi-docs/service-gateway-personal-mode.md
Service: powerbi
GitHub Login: @mgblythe
Microsoft Alias: mblythe

Thanks for your suggestion, @v-kerwan. We’ve forwarded your feedback to the writer, who should respond to this thread shortly. Thanks!

@v-kerwan - thanks, updated the doc

authors: maggiesMSFT mgblythe v-kerwan


text:
Count of throttling tooltip

I cannot see in the documentation where the definition of "count of throttled windows" appears.   This appears on the tooltip of the Overloaded minutes per hour visual within the performance app.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: e6f52eeb-717d-9a67-b775-c17c5cf916e4
Version Independent ID: 2c804bb2-1cf3-462e-730b-ecfbae2a5e9e
Content: Monitor Power BI Premium Gen2 capacities with the Gen2 metrics app. - Power BI
Content Source: powerbi-docs/admin/service-premium-gen2-metrics-app.md
Service: powerbi
Sub-service: powerbi-premium
GitHub Login: @KesemSharabi
Microsoft Alias: kesharab

Hi @roconnor39,
Thanks for your comment. I'll look into it and get back to you shortly.

Hi @roconnor39,
Thank you for pointing out that there's no definition for 'count of throttled windows'. This really should be renamed to Overloaded Minutes. The value is displayed in multiples of half a minute.
We'll shortly change the name in the tooltip so that it doesn't cause any further confusion.
Thanks,
Kesem

Hi @roconnor39,
Just to update you, the change is already live:

Thanks,
Kesem

Thanks for this.  Just to Clarify, the overloaded minutes - if each bar represents an hour, would the over loaded minutes tool tip not exceed 60 minutes - its just that the customer has claimed he has claimed more than 60 in an hour.
From: Kesem Sharabi @.>
Sent: 14 February 2022 06:54
To: MicrosoftDocs/powerbi-docs @.>
Cc: Rebecca OConnor @.>; Mention @.>
Subject: Re: [MicrosoftDocs/powerbi-docs] Count of throttling tooltip (Issue #3591)
Hi @roconnor39https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Froconnor39&data=04|01|roconnor%40microsoft.com|953f2928cb364264a55d08d9ef86bb0c|72f988bf86f141af91ab2d7cd011db47|1|0|637804184260008245|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=vjEbBwe%2BQTHo5oWUohVYNInaVd6b2NdP1vvkr3RAI3k%3D&reserved=0,
Just to update you, the change is already live:
[image]https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuser-images.githubusercontent.com%2F54834915%2F153814396-6485891f-0fe8-4561-8084-1b14742a9ee5.png&data=04|01|roconnor%40microsoft.com|953f2928cb364264a55d08d9ef86bb0c|72f988bf86f141af91ab2d7cd011db47|1|0|637804184260058233|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=yfyoXzFVLX3nUa%2BuXGTcPZ19djZiTK%2FnVqaI9Q%2FixdI%3D&reserved=0
Thanks,
Kesem

Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fpowerbi-docs%2Fissues%2F3591%23issuecomment-1038715318&data=04|01|roconnor%40microsoft.com|953f2928cb364264a55d08d9ef86bb0c|72f988bf86f141af91ab2d7cd011db47|1|0|637804184260058233|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=3Yy3KrDfb1VX%2B4SkUODw2ziBCqV8Nazp4OroGGrggHk%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAQ2QMML5RVEERVGNNTBKVXLU3CRHFANCNFSM5N2V24RQ&data=04|01|roconnor%40microsoft.com|953f2928cb364264a55d08d9ef86bb0c|72f988bf86f141af91ab2d7cd011db47|1|0|637804184260058233|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=pMB3l6irz1BZ4DRcQa1GOZ4WEOKbJDFcF3bUvdOToIQ%3D&reserved=0.
Triage notifications on the go with GitHub Mobile for iOShttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04|01|roconnor%40microsoft.com|953f2928cb364264a55d08d9ef86bb0c|72f988bf86f141af91ab2d7cd011db47|1|0|637804184260058233|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=pM01elB0pfOFNaHr6qb2FeT7%2BHMopemy2dDkXZTvCCw%3D&reserved=0 or Androidhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04|01|roconnor%40microsoft.com|953f2928cb364264a55d08d9ef86bb0c|72f988bf86f141af91ab2d7cd011db47|1|0|637804184260058233|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=3K0fDTYvpp3ZTUnD5QOkYtKnQ9gwqSDwVdbQSdgIqnE%3D&reserved=0.
You are receiving this because you were mentioned.Message ID: @.@.>>


text:
Update desktop-matrix-visual.md

Whether or not you keep the bullets, the suggestion is for images to follow the corresponding descriptive text.

@eric-urban : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@eric-urban ,
Thank you!  Your edits have been made and should go live tomorrow.

authors: PRMerger15 eric-urban mihart


text:
Lakehouse connector not visible

In my Fabric Trial environment the Fabric Lakehouse connector is not visible
[Enter feedback here]

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: c4bcc52c-fd62-970a-0d7d-bc179018cb6e
Version Independent ID: c4bcc52c-fd62-970a-0d7d-bc179018cb6e
Content: Power Query Lakehouse (Beta) connector - Power Query
Content Source: powerquery-docs/connectors/lakehouse.md
Service: powerquery
GitHub Login: @DougKlopfenstein
Microsoft Alias: dougklo

Hi @schofiep
This appears to be a customer support issue rather than a documentation issue. For information about customer support for Microsoft Fabric, go to Microsoft Fabric support.

authors: DougKlopfenstein schofiep

repo: MicrosoftDocs/powerquery-docs


text:
The term "ancilla" should be removed in favor of

[Enter feedback here]

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 61d86f1e-9754-01fb-3521-1edc2b72d532
Version Independent ID: 59733c91-9491-544f-6aba-e3049bcd464d
Content: Quantum characterization and statistics - Azure Quantum
Content Source: articles/user-guide/libraries/standard/characterization.md
Service: azure-quantum
Sub-service: qsharp-guide
GitHub Login: @Bradben
Microsoft Alias: martinro

Dupe

authors: Bradben cgranade

repo: MicrosoftDocs/quantum-docs


text:
Resolve syncing conflicts from repo_sync_working_branch to master

Pull request opened by Docs to resolve syncing conflicts from repo_sync_working_branch to master.

Docs Build status updates of commit 3aa9e6d:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/MicrosoftDocs/sccm-docs-powershell-ref, working directory: W:\x5c5-s, target branch: master, target branch commit: 5c4cc62706af0cf936c79e07d6e504df38ad3a0d, source commit: 3aa9e6d306247e3825945734f3317f9497b960b9.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

@Taojunshen : Thanks for your contribution! The author, @aczechowski, has been notified to review your proposed change.

Docs Build status updates of commit bd45af9:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/MicrosoftDocs/sccm-docs-powershell-ref, working directory: W:\u233-s, target branch: master, target branch commit: 5c4cc62706af0cf936c79e07d6e504df38ad3a0d, source commit: bd45af9b15c3b92c1e4e4f3f0513afdc5fc2779b.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

@Taojunshen : Thanks for your contribution! The author, @aczechowski, has been notified to review your proposed change.

Docs Build status updates of commit bd45af9:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/MicrosoftDocs/sccm-docs-powershell-ref, working directory: W:\0g13-s, target branch: master, target branch commit: dd249672a2bdc1682927a211a96c5302da7b4b7b, source commit: bd45af9b15c3b92c1e4e4f3f0513afdc5fc2779b.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

repo: MicrosoftDocs/sccm-docs-powershell-ref


text:
AdventureWorks DB

Hello,
I'm not sure if this is the correct repo to report this issue, if I need to post it somewhere else please feel free to advise.
I constantly refer to AdventureWorks as a "WWMD" (What would  Microsoft Do) of database design.  I'm also a big fan of Docker and being able to spin up and tear down resources at a moments notice.
On the SQL Server Linux pages, the AdventureWorks pages don't provide a docker image.  I realize that it's quite possible that such as an image doesn't exist or exist yet, but I do feel that it should and subsequently reflected in the documentation.
https://docs.microsoft.com/en-us/sql/samples/adventureworks-install-configure?view=sql-server-linux-ver15
Thanks,
Isaac Martinez

@rothja @MikeRayMSFT @MashaMSFT Making you aware of this user suggestion. I will close this issue as it is a big support-type issue.

@ikemtz I think this is a good idea for consideration. Thank you for your input. I am closing this now. If you wish to respond further, use the @ notification for further communication with each of us.

authors: CarlRabeler ikemtz

repo: MicrosoftDocs/sql-docs


text:
Typo

Rolling Upgrade - Missing space (SQL Serverinstance) in 2nd sentence.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 916e128d-19fd-1f7d-8285-6313c4419710
Version Independent ID: 8402af42-fdd1-2f3b-7c6a-8759e90e115f
Content: Choose a database engine upgrade method - SQL Server
Content Source: docs/database-engine/install-windows/choose-a-database-engine-upgrade-method.md
Product: sql
Technology: install
GitHub Login: @MashaMSFT
Microsoft Alias: mathoma

Hi @NuNn-DaDdY , thanks for contacting Microsoft and finding this typo! Did you want to make this change yourself? This will add you as a contributor to the article, and it's a very simple process.
To do so, please do the following:

Navigate to the page of interest
Select the "Edit" button at the top right of the page
Select the "Pencil" icon on the right
Modify the text within the text box in markdown format - more info: https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet
Name your file change and provide a description, if necessary
Select "Propose file change"
Select "Create pull request" on the 'Comparing changes' page
Select "Create pull request" on the 'Open a pull request' page

Please let me know if you wanted do it yourself, or I would be happy to do so.
Thanks!
Masha from the SQL Docs team

Good Afternoon Masha,
Sure - I'd be happy to create a pull request.  This has been completed and
a pull request has been created.  Thank you very much for the instructions
as well. Have a great day!
Best Regards,
Corey Nunnery
On Thu, Sep 19, 2019 at 1:11 PM Masha at MSFT notifications@github.com
wrote:

Hi @NuNn-DaDdY https://github.com/NuNn-DaDdY , thanks for contacting
Microsoft and finding this typo! Did you want to make this change yourself?
This will add you as a contributor to the article, and it's a very simple
process.
To do so, please do the following:

Navigate to the page of interest
Select the "Edit" button at the top right of the page
Select the "Pencil" icon on the right
Modify the text within the text box in markdown format - more info:
https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet
Name your file change and provide a description, if necessary
Select "Propose file change"
Select "Create pull request" on the 'Comparing changes' page
Select "Create pull request" on the 'Open a pull request' page

Please let me know if you wanted do it yourself, or I would be happy to do
so.
Thanks!
Masha from the SQL Docs team
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/sql-docs/issues/3015?email_source=notifications&email_token=AA4EAAMWDUB7ONAE7VZECTLQKOXCHA5CNFSM4IYMZWQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7EFYKQ#issuecomment-533224490,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA4EAAOUJQNUDVECINACXBDQKOXCHANCNFSM4IYMZWQA
.

Hi @NuNn-DaDdY , awesome, thank you so much! I've signed off on the PR and you should see the change live in the next two business days :) Thanks again for making our documentation better! I will proceed with closing out this Git Issue but please feel free to reply should you need anything further.
Thanks!
Masha from the SQL Docs team

authors: MashaMSFT NuNn-DaDdY


text:
Documentation Mistake !!

db_accessadmin is the database permission that will enable the database account to add new members to the partially contained database Not db_securityadmin !
i think the paragraph wording is not clear.
Regards,
Emad Al-Mousa

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: b9d16565-6317-df2b-41d7-701eb83fb90b
Version Independent ID: 8fcc2424-a8b4-f188-dceb-e3aebd2b49ff
Content: Security Best Practices with Contained Databases - SQL Server
Content Source: docs/relational-databases/databases/security-best-practices-with-contained-databases.md
Product: sql
Technology: security
GitHub Login: @VanMSFT
Microsoft Alias: vanto

@emad-almousa -- Emad, thank you for your feedback.
@VanMSFT -- Van, please look into this issue 3810.

@emad-almousa - Hi Emad Al-Mousa! Thank you! You're right, and I've fixed the text to reflect db_accessadmin instead of db_securityadmin. It should be live soon. Thanks again for your help on our documentation!
https://github.com/MicrosoftDocs/sql-docs-pr/pull/13274

authors: VanMSFT WilliamAntonRohm emad-almousa


text:
SSMS 19.1 is stuck on loading packages

I removed my old instance of SSMS and all associated files. When I try to install the new version it gets stuck on the loading packages page. So I deleted that install package from downloads, restarted my laptop and attempted to retry the install. Now the install goes straight to the loading packages section and stays there for hours.
How do I fix this? I need SSMS for school.

Had to do a system restore to resolve the issue.

Closing issue


text:
RDCMan - Support for AAD auth

The Remote Desktop Client supports AAD auth by adding enablerdsaadauth in the connection file. Would be nice if RDCMan would have an option to enable this in connections.
Even better if we could supply a login_hint to the process, but I think that's not an option available in mstsc.
Source: https://learn.microsoft.com/en-us/windows/client-management/client-tools/connect-to-remote-aadj-pc

See  - RDCman 2.93 does allow some Azure VMs to connect with Azure creds.

still an issue as of 10/8/2024 - Azure based VM's using SSO do work with RDCMan - Intune/Autopiloted devices do not.

authors: andrasg barnabyibis michaeldeblok

repo: MicrosoftDocs/sysinternals


text:
Windows Terminal Settings not accessible via the instructions given

[Enter feedback here]
There is no settings dropdown in windows terminal. Unable to locate the settings.json. Search of the system doesn't work

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: ee133b07-2c89-7f9e-4ab4-dd682c21c37a
Version Independent ID: d7838521-160a-6b6e-6795-a8049f18ede6
Content: Windows Terminal installation
Content Source: TerminalDocs/install.md
Product: dev-environment
Technology: windows-terminal
GitHub Login: @cinnamon-msft
Microsoft Alias: cinnamon

@tonydattolo can you share a screenshot of your Terminal window?
If you right-click an empty spot on the title bar, can you access Settings that way?

That is the original Windows Console, not the new Terminal.
Old

New

On the version of Windows you are using, you will only be running Windows Terminal if you explicitly install it (from the Store at https://aka.ms/terminal) and then launch it instead of Command Prompt or PowerShell.

authors: DHowett tonydattolo

repo: MicrosoftDocs/terminal


text:
Videos Not Working

Under all 3 sections, the first video of each section is not working at all. grey box showing the URL.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: dd6ebefd-fcc0-7e65-6450-c5908dbb61f8
Version Independent ID: 83656699-f59b-5c22-94ad-bb2c8d58b2ae
Content: What's new in Visual Studio 2019
Content Source: docs/ide/whats-new-visual-studio-2019.md
Product: visual-studio-windows
Technology: vs-ide-general
GitHub Login: @TerryGLee
Microsoft Alias: tglee

@DaDDyICEPOC Thanks for letting us know. Unfortunately, I can't reproduce what you describe; the videos look to be working as intended in the following browsers: Edge, Chrome, and Firefox running on Windows 10. What browser and operating system are you using?

Hi Terry,
My apologies. Turns out it is a filter our end. I got confused as I can get to youtube but I have just been told that is a manual exception in our filtering.
Again, my apologies for any confusion caused 😊
Many Thanks
POC
Paul O'Connor|Business Intelligence Analyst|Mirus IT Solutions
E: Paul.Oconnor@mirus-it.com|T: 01908 257362
All views expressed in this message are those of the individual sender, not The Mirus Trading Group Ltd or any subsidiaries or associated companies. The information in this e-mail may be confidential and privileged. If you are not the intended recipient please notify us immediately by telephoning 01908 257352. You should not copy this e-mail or use it for any other purposes nor disclose its contents to any other person. Although this e-mail and any attachments are believed to be free of any virus, or any other defect that might affect any other computer or IT system into which they are received and opened, it is the responsibility of the recipient to ensure that they have antivirus protection. No responsibility is accepted by The Mirus Trading Group Ltd or any subsidiaries or associated companies for any loss or damage arising in any way from receipt or use thereof. If we receive an email from you or send an email to you, we process your personal information, such as your email address and contact details. We only process personal information in accordance with our Privacy Notice, which can be found here https://www.mirus-it.co.uk/Privacy-Policy
The Mirus Trading Group Ltd is a company registered in England and Wales with a company number of 7545679, its registered office is 7,Clarendon Drive, Wymbush, Milton Keynes. MK8 8ED.
From: Terry G. Lee notifications@github.com
Sent: 05 April 2019 14:45
To: MicrosoftDocs/visualstudio-docs visualstudio-docs@noreply.github.com
Cc: Paul O'Connor Paul.Oconnor@mirus-it.com; Mention mention@noreply.github.com
Subject: Re: [MicrosoftDocs/visualstudio-docs] Videos Not Working (#3004)
This message originated outside of your organisation

@DaDDyICEPOChttps://github.com/DaDDyICEPOC Thanks for letting us know. Unfortunately, I can't reproduce what you describe; the videos look to be working as intended in the following browsers: Edge, Chrome, and Firefox running on Windows 10. What browser and operating system are you using?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/visualstudio-docs/issues/3004#issuecomment-480280815, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AtZCNdKmEG6xp4utzQ5ImiBEhwwttOgcks5vd1NugaJpZM4ceZe7.

authors: DaDDyICEPOC TerryGLee

repo: MicrosoftDocs/visualstudio-docs


text:
What are the "vstest.console.exe" command line versions of "rerunFailedTests: true" and "rerunMaxAttempts: 3"

https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/test/visual-studio-test-agent-deployment?view=azure-devops
I would like to use the VSTEST test options "rerunFailedTests: true" and "rerunMaxAttempts: 3".
however we have some cases where our YAML build runs a bash script to copy tests and select what tests to run, then call "vstest.console.exe" to run the tests.
What are the "vstest.console.exe" command line versions of "rerunFailedTests: true" and "rerunMaxAttempts: 3"
Same question for "dotnet.exe test" command line options, as we use that in some cases as well?
Thanks,
Brian.

@BrianMouncer - these options are currently only supported through the VSTest task, not throught the CLI. If you need this on the CLI, request you to open a feature request on the test platform repo.
https://github.com/microsoft/vstest
@TerryGLee - this issue on the pipeline docs can be closed.

Closing per request.

authors: BrianMouncer PBoraMSFT TerryGLee


text:
Incorrect XML element

The <StartPrograms>...</StartPrograms> is incorrect. It should be <StartProgram>...</StartProgram>

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: aa63b4dc-21b4-307f-61d3-a13ce9d0475a
Version Independent ID: de62d1bc-6f08-edf9-9624-fee65b90185e
Content: How to Roundtrip Extensions - Visual Studio
Content Source: docs/extensibility/how-to-roundtrip-VSIXs.md
Product: visual-studio-windows
Technology: vs-ide-sdk
GitHub Login: @willbrown
Microsoft Alias: madsk

@carlos-quintero -- Carlos, thank you for your feedback.
@madskristensen -- Mads, please review my correction in the above-mentioned PR 5800.

@WilliamAntonRohm done


text:
Create a timed math quiz

[Enter feedback here]

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: ac26546d-191a-6600-a683-db4fbc5f4e46
Version Independent ID: d3341bf4-795c-0854-a272-8a9cc906976d
Content: Step 7: Add multiplication and division problems - Visual Studio
Content Source: docs/ide/step-7-add-multiplication-and-division-problems.md
Product: visual-studio-windows
Technology: vs-ide-general
GitHub Login: @ornellaalt
Microsoft Alias: ornella

@nuruddeen96 -- thank you for writing.  Please provide some details about your task.  Meanwhile, consider these resources:

Visual Studio on Q&A
Visual Studio MSDN Forum
Stack Overflow
Reddit


text:
Repo sync for protected CLA branch

The pull request is created from main638034627437158365sync_temp to main to fix git push error for protected CLA branch

Learn Build status updates of commit 5b6d76b:
:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


text:
Add note that the Just-In-Time component is required

The Just-In-Time debugger is only installed if you install certain feature packages for Visual Studio (E.G. C# development or C++ Desktop development). If it is not installed the Just-In-Time section is missing from Options > Debug. It would be helpful to note that if this doesnt exist the user should ensure the component is installed. (Or potentially update VS to explain that there are no options because it is not installed).
I was trying to debug an IIS website crash, and so had only installed the ASP.NET development module. Without clicking on another feature package in the installer and seeing that there is a Just-In-Time debugger option that is added it is not obvious that this is a component that needs to be installed.

@Mikejo5000
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off Thanks for the doc update, @AWilco !


text:
Provide GitHub login for VSCode Marketplace review/rating system

Allow users to login with their GitHub accounts to review and rate marketplace extensions. Just like I logged into my GitHub account to be able to write this feedback.
This feature will make it less of a hassle for users to better engage with the marketplace.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 145e9748-0039-e0df-2bc1-7ad5e74ab75a
Version Independent ID: cf629735-b15d-3948-86a3-6fffe25ec0ae
Content: Marketplace support
Content Source: docs/marketplace/marketplace-billing-qa.md
Product: devops
GitHub Login: @elbatk
Microsoft Alias: elbatk

Hi @NikolasKomonen , I'm going to tag @harishkragarwal here for awareness, but in the future product suggestions should go to the Azure DevOps developer community.

@elbatk Thanks for pointing me in the right direction.

@NikolasKomonen: thanks for the suggestion. We have this on our backlog and wish to enable it soon.

authors: NikolasKomonen elbatk harishkragarwal

repo: MicrosoftDocs/vsts-docs


text:
Passing environment variables as parameters

Hi,
The documented example example indicates that a mapping of environment variables can be used.
env:  # mapping of environment variables to add

Is it possible to parameterise this by passing a mapping, as I cannot get this to work based on the example docs.
For example;
# StepTemplate.yml

parameters:
    PassedVariables: {}

steps:
    - task: PowerShell@2
     # snip #
        inputs:
            targetType: 'filePath'
            filePath: MyExampleScript.ps1
            env:
            ${{ insert }}: ${{ parameters.PassedVariables }}

# EntryPoint.yml
jobs:
  - job: MyTestJob
    # snip
    - template: StepTemplate.yml
        variables:
            SomeVariable: 'This is an example variable'
        parameters:
            PassedVariables:
                Var1: 'Hello World'
                Var2: $(SomeVariable)

The issue I am having is, I was expecting that when I run my script I can echo the $ENV:XXX variable but it doesn't seem to work correctly, probaly an ID10T error but where am I going wrong?
# MyExampleScript.ps1
Write-Host "$ENV:Var1 $ENV:Var2" # Doesnt work :(
Write-Host "$Var1 $Var2" # I never expected this to work but tried anyways

Apologies for the short example, hopefully makes sense, otherwise I can expand upon it later.
Thanks.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: a0e444c2-69c6-4d71-6fd0-94d0f4097d3a
Version Independent ID: 3a727833-1cc3-c2fb-c5b3-22605eee2721
Content: PowerShell task - Azure Pipelines
Content Source: docs/pipelines/tasks/utility/powershell.md
Product: devops
GitHub Login: @andyjlewis
Microsoft Alias: alewis

I think you're really close, just have a syntax problem with env -- it's a peer of inputs. Here's what worked for me:
# azure-pipelines.yml
steps:
- checkout: none
- template: template.yml
  parameters:
    PassedVariables:
      Var1: 'Hello World'
      Var2: 'Foo bar'

# template.yml
parameters:
  PassedVariables: {}

steps:
- task: PowerShell@2
  inputs:
    targetType: 'inline'
    script: |
      Get-ChildItem Env:
  env:
    ${{ insert }}: ${{ parameters.PassedVariables }}

authors: MAHDTech vtbassmatt