Azure Automation Runbooks moving to GitHub

Published Jan 07 2021 02:12 AM 30.9K Views
Microsoft

TechNet Script Center gallery hosting Automation scripts (runbooks) as shown in the Runbooks Gallery is set to retire by December 2020. You can go through the official announcement here by the TechNet team. It entails that all PowerShell & Python scripts available at Script Center gallery would have to be moved to another location. We’ve chosen GitHub as the new source for all Azure the TechNet gallery here. We chose GitHub due to the various benefits offered by the platform around making it easy to contribute to your open-source projects, showcase your work to the community, track down issues, documentation etc.

The change would go live by Jan 15, 2021.

 

How will it look like?

Today, there are more than 700 Azure Scripts owned by  various Product Teams at Microsoft as well as external contributors. These scripts are accessed by the customers through the Runbook Gallery blade of the Automation account in the Azure Portal. The Source filter, previously shown as Script Center would be replaced by GitHub as shown below. The workflow will be integrated with GitHub moving forward.

 

Picture1.jpg

 

Upon selecting a runbook, “View Source Project” will take you to the GitHub repository for that script. Runbooks displayed from Source PowerShell Gallery will remain as-is without any changes.

 

Picture2.jpg

Picture2.jpg

What will change?

Summarizing the changes that you will see in the script migration from Script Center to GitHub below:

  • The Top-level GitHub organization would be azureautomation
  • Each Script Center script would be a repository created with the same name as the script under “azureautomation” organization.
  • All the scripts will have a GitHub Topic as "azureautomationrunbookgallery".
  • Script center license would be moved to the GitHub License.md file.
  • All the script metadata fields in script center such as Author, rating, downloads, summary, category, sub-category, tags etc. would be added to the GitHub Metadata.json file.
  • Readme.md file holds the script description & a note for scripts have been migrated from Script Center.

TechNet gallery is retiring! This script was migrated from TechNet script center to GitHub by Microsoft Azure Automation product group. All the Script Center fields like Rating, Rating Count and Download Count have been carried over to GitHub as-is for the migrated scripts only. Note: The Script Center fields will not be applicable for the new repositories created in GitHub & hence those fields will not show up for new GitHub repositories.”

  • Script center Q&A will not be moved to GitHub. You can instead use GitHub tracker called Issues which is a great way to keep track of tasks, enhancements, and bugs for your projects.
  • New Scripts (Runbooks) synced from GitHub to the Runbook Gallery won’t have Rating & downloads field as these fields are specific to Script Center and not GitHub. You’d only see Created By & Last updated field for GitHub scripts.

 

What to do next?

 

If you want to contribute to an existing runbook: 

You can either raise a PR with the changes or create a fork out of the repository.

Note: If you fork the repository, the runbook maybe be shown twice on the Automation runbook gallery (One of them would be the original and other one would be the forked one.)2.

 

If you want to author a new runbook for runbook gallery:

  • Create a public repository on GitHub and add the runbook, readme.md, description etc.
  • Add the topic “azureautomationrunbookgallery” to make sure it is discovered by our service and displayed in the Automation Runbook gallery.
  • If the runbook that you created is a PowerShell workflow or a python 3 runbook add the topic “PowerShellWorkflow” or “Python3” respectively. No specific Topic is needed for PowerShell runbooks. These Topics would be used for categorization & search operation in the Runbook Gallery.
  • Sync duration between GitHub & Automation Runbook Gallery would be 12 hours for updated and new added runbooks.
  • We strongly encourage you to contribute & help grow the Azure Automation community. Share the amazing work you’ve been doing with the runbooks with the community members. Your contributions would be appreciated!
  • Please don’t forget to “star” rate the repository if you use or like it or it helped you with your scenario. This will help us improve our categorization workflow within Runbook Gallery and show you the most popular scripts first. 

Happy Automation!

 

Learn more about Azure Automation.

1 Comment

Hi,

 

I followed all the recommended steps to create a new Powershell Workflow runbook. It appears in the library on the portal and it appears in the github library.

 

However, it's not recognized as a Powershell Workflow, it's only recognized as a regular powershell script, not a powershell workflow and due to that, it doesn't work very well.

 

What's the solution for this problem?

The repo is https://github.com/DennesTorres/ReIndex-AzureSQL-Tables-When-Needed/ and it alreay appears on the github automation gallery in the azure portla, but it's not recognized correctly.

 

%3CLINGO-SUB%20id%3D%22lingo-sub-2039337%22%20slang%3D%22en-US%22%3EAzure%20Automation%20Runbooks%20moving%20to%20GitHub%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2039337%22%20slang%3D%22en-US%22%3E%3CP%3ETechNet%20Script%20Center%20gallery%20hosting%20Automation%20scripts%20(runbooks)%20as%20shown%20in%20the%20Runbooks%20Gallery%20is%20set%20to%20retire%20by%20December%202020.%20You%20can%20go%20through%20the%20official%20announcement%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fteamblog%2Ftechnet-gallery-retirement%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehere%3C%2FA%3E%20by%20the%20TechNet%20team.%20It%20entails%20that%20all%20PowerShell%20%26amp%3B%20Python%20scripts%20available%20at%20Script%20Center%20gallery%20would%20have%20to%20be%20moved%20to%20another%20location.%20We%E2%80%99ve%20chosen%20GitHub%20as%20the%20new%20source%20for%20all%20Azure%20the%20TechNet%20gallery%20%3CA%20href%3D%22https%3A%2F%2Fgallery.technet.microsoft.com%2Fscriptcenter%2Fsite%2Fsearch%3Ff%255B0%255D.Type%3DRootCategory%26amp%3Bf%255B0%255D.Value%3DWindowsAzure%26amp%3Bf%255B0%255D.Text%3DWindows%2520Azure%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehere%3C%2FA%3E.%20We%20chose%20GitHub%20due%20to%20the%20various%20benefits%20offered%20by%20the%20platform%20around%20making%20it%20easy%20to%20contribute%20to%20your%20open-source%20projects%2C%20showcase%20your%20work%20to%20the%20community%2C%20track%20down%20issues%2C%20documentation%20etc.%3C%2FP%3E%0A%3CP%3EThe%20change%20would%20go%20live%20by%20Jan%2015%2C%202021.%3C%2FP%3E%0A%3CH3%20id%3D%22toc-hId-1943465775%22%20id%3D%22toc-hId-1943465805%22%20id%3D%22toc-hId-1943465805%22%20id%3D%22toc-hId-1943465805%22%3E%26nbsp%3B%3C%2FH3%3E%0A%3CH3%20id%3D%22toc-hId-136011312%22%20id%3D%22toc-hId-136011342%22%20id%3D%22toc-hId-136011342%22%20id%3D%22toc-hId-136011342%22%3E%3CFONT%20size%3D%225%22%3EHow%20will%20it%20look%20like%3F%3C%2FFONT%3E%3C%2FH3%3E%0A%3CP%3E%3CSPAN%3EToday%2C%20there%20are%20more%20than%20700%20Azure%20Scripts%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%3Eowned%20by%E2%80%AF%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fgallery.technet.microsoft.com%2Fscriptcenter%2Fsite%2Fsearch%3Ff%255b0%255d.Type%3DRootCategory%26amp%3Bf%255b0%255d.Value%3DWindowsAzure%26amp%3Bf%255b0%255d.Text%3DWindows%2520Azure%26amp%3Bf%255b1%255d.Type%3DSubCategory%26amp%3Bf%255b1%255d.Value%3DWindowsAzure_automation%26amp%3Bf%255b1%255d.Text%3DAutomation%26amp%3Bf%255b2%255d.Type%3DUser%26amp%3Bf%255b2%255d.Value%3DAzure%2520Automation%2520Product%2520Team%26amp%3Bf%255b2%255d.Text%3DAzure%2520Automation%2520Product%2520Team%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3E%3CSPAN%3E%26nbsp%3Bvarious%20Product%20Teams%20at%E2%80%AF%3C%2FSPAN%3E%3C%2FA%3E%3CA%20href%3D%22https%3A%2F%2Fgallery.technet.microsoft.com%2Fscriptcenter%2Fsite%2Fsearch%3Ff%255b0%255d.Type%3DRootCategory%26amp%3Bf%255b0%255d.Value%3DWindowsAzure%26amp%3Bf%255b0%255d.Text%3DWindows%2520Azure%26amp%3Bf%255b1%255d.Type%3DSubCategory%26amp%3Bf%255b1%255d.Value%3DWindowsAzure_automation%26amp%3Bf%255b1%255d.Text%3DAutomation%26amp%3Bf%255b2%255d.Type%3DContributors%26amp%3Bf%255b2%255d.Value%3DMicrosoft%26amp%3Bf%255b2%255d.Text%3DMicrosoft%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3E%3CSPAN%3EMicrosoft%3C%2FSPAN%3E%3C%2FA%3E%3CSPAN%3E%E2%80%AFas%20well%20as%20external%20contributors.%E2%80%AFThese%20scripts%20are%20accessed%20by%20the%20customers%20through%20the%20Runbook%20Gallery%20blade%20of%20the%20Automation%20account%20in%20the%20Azure%20Portal.%26nbsp%3B%3C%2FSPAN%3EThe%20Source%20filter%2C%20previously%20shown%20as%20Script%20Center%20would%20be%20replaced%20by%20GitHub%20as%20shown%20below.%20The%20workflow%20will%20be%20integrated%20with%20GitHub%20moving%20forward.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Picture1.jpg%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F244717iA194C65E0DF66308%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22Picture1.jpg%22%20alt%3D%22Picture1.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CDIV%20id%3D%22tinyMceEditorJaspkaur_1%22%20class%3D%22mceNonEditable%20lia-copypaste-placeholder%22%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CP%3EUpon%20selecting%20a%20runbook%2C%20%E2%80%9CView%20Source%20Project%E2%80%9D%20will%20take%20you%20to%20the%20GitHub%20repository%20for%20that%20script.%20Runbooks%20displayed%20from%20Source%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fwww.powershellgallery.com%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3EPowerShell%20Gallery%3C%2FA%3E%20will%20remain%20as-is%20without%20any%20changes.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Picture2.jpg%22%20style%3D%22width%3A%20910px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F244718iAB292701958B5615%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22Picture2.jpg%22%20alt%3D%22Picture2.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Picture2.jpg%22%20style%3D%22width%3A%200px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F244715i10CAA11811B46013%2Fimage-size%2Fsmall%3Fv%3D1.0%26amp%3Bpx%3D200%22%20width%3D%220%22%20height%3D%220%22%20role%3D%22button%22%20title%3D%22Picture2.jpg%22%20alt%3D%22Picture2.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3E%3CFONT%20size%3D%225%22%3EWhat%20will%20change%3F%3C%2FFONT%3E%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3ESummarizing%20the%20changes%20that%20you%20will%20see%20in%20the%20script%20migration%20from%20Script%20Center%20to%20GitHub%20below%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EThe%20Top-level%20GitHub%20organization%20would%20be%20%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2Fazureautomation%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Eazureautomation%3C%2FA%3E%3C%2FLI%3E%0A%3CLI%3EEach%20Script%20Center%20script%20would%20be%20a%20repository%20created%20with%20the%20same%20name%20as%20the%20script%20under%20%E2%80%9Cazureautomation%E2%80%9D%20organization.%3C%2FLI%3E%0A%3CLI%3EAll%20the%20scripts%20will%20have%20a%20GitHub%20Topic%20as%20%22azureautomationrunbookgallery%22.%3C%2FLI%3E%0A%3CLI%3EScript%20center%20license%20would%20be%20moved%20to%20the%20GitHub%20License.md%20file.%3C%2FLI%3E%0A%3CLI%3EAll%20the%20script%20metadata%20fields%20in%20script%20center%20such%20as%20Author%2C%20rating%2C%20downloads%2C%20summary%2C%20category%2C%20sub-category%2C%20tags%20etc.%20would%20be%20added%20to%20the%20GitHub%20Metadata.json%20file.%3C%2FLI%3E%0A%3CLI%3EReadme.md%20file%20holds%20the%20script%20description%20%26amp%3B%20a%20note%20for%20scripts%20have%20been%20migrated%20from%20Script%20Center.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CEM%3E%E2%80%9D%3C%2FEM%3E%3CEM%3E%20TechNet%20gallery%20is%20retiring!%20This%20script%20was%20migrated%20from%20TechNet%20script%20center%20to%20GitHub%20by%20Microsoft%20Azure%20Automation%20product%20group.%20All%20the%20Script%20Center%20fields%20like%20Rating%2C%20Rating%20Count%20and%20Download%20Count%20have%20been%20carried%20over%20to%20GitHub%20as-is%20for%20the%20migrated%20scripts%20only.%20Note%3A%20The%20Script%20Center%20fields%20will%20not%20be%20applicable%20for%20the%20new%20repositories%20created%20in%20GitHub%20%26amp%3B%20hence%20those%20fields%20will%20not%20show%20up%20for%20new%20GitHub%20repositories.%E2%80%9D%3C%2FEM%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EScript%20center%20Q%26amp%3BA%20will%20not%20be%20moved%20to%20GitHub.%20You%20can%20instead%20use%20GitHub%20tracker%20called%20Issues%20which%20is%20a%20great%20way%20to%20keep%20track%20of%20tasks%2C%20enhancements%2C%20and%20bugs%20for%20your%20projects.%3C%2FLI%3E%0A%3CLI%3ENew%20Scripts%20(Runbooks)%20synced%20from%20GitHub%20to%20the%20Runbook%20Gallery%20won%E2%80%99t%20have%20Rating%20%26amp%3B%20downloads%20field%20as%20these%20fields%20are%20specific%20to%20Script%20Center%20and%20not%20GitHub.%20You%E2%80%99d%20only%20see%20Created%20By%20%26amp%3B%20Last%20updated%20field%20for%20GitHub%20scripts.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CH3%20id%3D%22toc-hId--1671443151%22%20id%3D%22toc-hId--1671443121%22%20id%3D%22toc-hId--1671443121%22%20id%3D%22toc-hId--1671443121%22%3E%26nbsp%3B%3C%2FH3%3E%0A%3CH3%20id%3D%22toc-hId-816069682%22%20id%3D%22toc-hId-816069712%22%20id%3D%22toc-hId-816069712%22%20id%3D%22toc-hId-816069712%22%3E%3CFONT%20size%3D%225%22%3E%3CSTRONG%3EWhat%20to%20do%20next%3F%3C%2FSTRONG%3E%3C%2FFONT%3E%3C%2FH3%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EIf%20you%20want%20to%20contribute%20to%20an%20existing%20runbook%3A%26nbsp%3B%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EYou%20can%20either%20raise%20a%20PR%20with%20the%20changes%20or%20create%20a%20fork%20out%20of%20the%20repository.%3C%2FP%3E%0A%3CP%3ENote%3A%20If%20you%20fork%20the%20repository%2C%20the%20runbook%20maybe%20be%20shown%20twice%20on%20the%20Automation%20runbook%20gallery%20(One%20of%20them%20would%20be%20the%20original%20and%20other%20one%20would%20be%20the%20forked%20one.)2.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EIf%20you%20want%20to%20author%20a%20new%20runbook%20for%20runbook%20gallery%3A%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3ECreate%20a%20public%20repository%20on%20GitHub%20and%20add%20the%20runbook%2C%20readme.md%2C%20description%20etc.%3C%2FLI%3E%0A%3CLI%3EAdd%20the%20topic%20%E2%80%9Cazureautomationrunbookgallery%E2%80%9D%20to%20make%20sure%20it%20is%20discovered%20by%20our%20service%20and%20displayed%20in%20the%20Automation%20Runbook%20gallery.%3C%2FLI%3E%0A%3CLI%3EIf%20the%20runbook%20that%20you%20created%20is%20a%20PowerShell%20workflow%20or%20a%20python%203%20runbook%20add%20the%20topic%20%E2%80%9CPowerShellWorkflow%E2%80%9D%20or%20%E2%80%9CPython3%E2%80%9D%20respectively.%20No%20specific%20Topic%20is%20needed%20for%20PowerShell%20runbooks.%20These%20Topics%20would%20be%20used%20for%20categorization%20%26amp%3B%20search%20operation%20in%20the%20Runbook%20Gallery.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CUL%20class%3D%22lia-list-style-type-circle%22%3E%0A%3CLI%3ESync%20duration%20between%20GitHub%20%26amp%3B%20Automation%20Runbook%20Gallery%20would%20be%2012%20hours%20for%20updated%20and%20new%20added%20runbooks.%3C%2FLI%3E%0A%3CLI%3EWe%20strongly%20encourage%20you%20to%20contribute%20%26amp%3B%20help%20grow%20the%20Azure%20Automation%20community.%20Share%20the%20amazing%20work%20you%E2%80%99ve%20been%20doing%20with%20the%20runbooks%20with%20the%20community%20members.%20Your%20contributions%20would%20be%20appreciated!%3C%2FLI%3E%0A%3CLI%3EPlease%20don%E2%80%99t%20forget%20to%20%E2%80%9Cstar%E2%80%9D%20rate%20the%20repository%20if%20you%20use%20or%20like%20it%20or%20it%20helped%20you%20with%20your%20scenario.%20This%20will%20help%20us%20improve%20our%20categorization%20workflow%20within%20Runbook%20Gallery%20and%20show%20you%20the%20most%20popular%20scripts%20first.%26nbsp%3B%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3EHappy%20Automation!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ELearn%20more%20about%20Azure%20Automation.%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CA%20href%3D%22https%3A%2F%2Fazure.microsoft.com%2Fen-in%2Fservices%2Fautomation%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EGet%20started%20with%20Automation.%3C%2FA%3E%3C%2FLI%3E%0A%3CLI%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-in%2Fazure%2Fautomation%2Flearn%2Fautomation-tutorial-runbook-textual-powershell%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EHow%20to%20create%20runbooks%3C%2FA%3E%3C%2FLI%3E%0A%3CLI%3EAutomation%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fautomation%2Fautomation-runbook-types%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Erunbook%20types%3C%2FA%3E%20%26amp%3B%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fautomation%2Fautomation-runbook-gallery%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Emodules%3C%2FA%3E%3C%2FLI%3E%0A%3C%2FUL%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-2039337%22%20slang%3D%22en-US%22%3E%3CP%3E%3CBR%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-left%22%20image-alt%3D%22201711-Azure-Automation.png%22%20style%3D%22width%3A%20734px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F244713iCB827ACA1CF4074B%2Fimage-dimensions%2F734x367%3Fv%3D1.0%22%20width%3D%22734%22%20height%3D%22367%22%20role%3D%22button%22%20title%3D%22201711-Azure-Automation.png%22%20alt%3D%22201711-Azure-Automation.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EGitHub%20would%20be%20the%20new%20source%20for%20all%20Azure%20Automation%20scripts%20aka%20runbooks%20present%20at%20the%20TechNet%20gallery!%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2039337%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EGovernance%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EManagement%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2435547%22%20slang%3D%22en-US%22%3ERe%3A%20Azure%20Automation%20Runbooks%20moving%20to%20GitHub%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2435547%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20followed%20all%20the%20recommended%20steps%20to%20create%20a%20new%20Powershell%20Workflow%20runbook.%20It%20appears%20in%20the%20library%20on%20the%20portal%20and%20it%20appears%20in%20the%20github%20library.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EHowever%2C%20it's%20not%20recognized%20as%20a%20Powershell%20Workflow%2C%20it's%20only%20recognized%20as%20a%20regular%20powershell%20script%2C%20not%20a%20powershell%20workflow%20and%20due%20to%20that%2C%20it%20doesn't%20work%20very%20well.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWhat's%20the%20solution%20for%20this%20problem%3F%3CBR%20%2F%3E%3CBR%20%2F%3EThe%20repo%20is%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2FDennesTorres%2FReIndex-AzureSQL-Tables-When-Needed%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgithub.com%2FDennesTorres%2FReIndex-AzureSQL-Tables-When-Needed%2F%3C%2FA%3E%26nbsp%3Band%20it%20alreay%20appears%20on%20the%20github%20automation%20gallery%20in%20the%20azure%20portla%2C%20but%20it's%20not%20recognized%20correctly.%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Version history
Last update:
‎Jan 07 2021 02:21 AM
Updated by: