Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MS Defender for Cloud - GitHub repos Limitations #100739

Closed
wants to merge 1 commit into from

Conversation

arindam0310018
Copy link
Contributor

Hello Team,
I did my Testing on the Recent released topic in MS Ignite 2022 - Connect your GitHub repositories to Microsoft Defender for Cloud I also prepared a blog for the same - https://github.com/arindam0310018/14-Oct-2022-DevOps__MS-Defender-4-Cloud-DevOps-Secuirty-In-GitHub

Limitations included in the PR is listed in your documentation

Request you to please include in the documentation.

Many Thanks
Regards, Arindam Mitra

Hello Team,
I did my Testing on the Recent released topic in MS Ignite 2022 - Connect your GitHub repositories to Microsoft Defender for Cloud
I also prepared a blog for the same - https://github.com/arindam0310018/14-Oct-2022-DevOps__MS-Defender-4-Cloud-DevOps-Secuirty-In-GitHub

Limitations included in the PR is listed in your documentation

Request you to please include in the documentation.

Many Thanks
Regards, Arindam Mitra
@prmerger-automator
Copy link
Contributor

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

@opbld30
Copy link

opbld30 commented Oct 31, 2022

Learn Build status updates of commit c92e5ba:

✅ Validation status: passed

File Status Preview URL Details
articles/defender-for-cloud/quickstart-onboard-github.md ✅Succeeded

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:

@jborsecnik jborsecnik added the aq-pr-triaged tracking label for the PR review team label Oct 31, 2022
@jborsecnik
Copy link
Contributor

@arindam0310018 @ElazarK, the images in this PR need to be moved to an appropriate media folder in this repo. This PR should also be submitted to the private repo, so it can go through staging and validation. Can you do that? Thanks.

@ElazarK
Copy link
Contributor

ElazarK commented Nov 2, 2022

@arindam0310018 this issue was handled in your other PR. I spoke with the principal PM and he did not want to add all of this information. I have already added and merged the relevant information to the docs so this PR is unnecessary at this point.

@ElazarK
Copy link
Contributor

ElazarK commented Nov 2, 2022

#please-close

@arindam0310018
Copy link
Contributor Author

Hello,
This was closed based on the update #100017

Best Regards, Arindam Mitra

@arindam0310018
Copy link
Contributor Author

Hello @ElazarK
Thank you for making the changes in the documentation.
I have updated the thread - #100017

Best Regards, Arindam Mitra

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants