#isve��

[toupee-or-nottoupee]

just a funny thing i had a thought abt. it does not actually "sense" too differently in my head. its just the sudden proximity that gets to him. If anyone not in the group does this, it's on sight 💥

[dovecandy]

old doodle page i just realized i never posted :thumbsup:

drew these while watching an impulse stream several months ago (very silly you should check out the vod on isv2 hastag not spon)

[mybeautifulchristianjourney]

The Ark of the Covenant

1 Bezalel made the ark of acacia wood two and a half cubits long, one and a half cubits wide, and one and a half cubits high. 2 He overlaid it with pure gold, inside and outside, and made a gold molding around it. 3 He cast four rings for it on its four feet, two rings on one side of it and two rings on its other side. 4 He made poles of acacia wood and overlaid them with gold. 5 He put the poles into the rings on the sides of the ark to carry it.

6 He made a Mercy Seat of pure gold two and a half cubits long and one and a half cubits wide. 7 He made two cherubim of gold; he made them of hammered work at the two ends of the Mercy Seat. 8 One cherub was at one end and one cherub at the other end. He made the cherubim at the two ends of the Mercy Seat and of one piece with it. 9 The cherubim had their wings spread upward, covering the Mercy Seat with their wings and facing each other. The faces of the cherubim were turned toward the Mercy Seat.

The Table of Showbread

10 Then he made a table of acacia wood two cubits long, one cubit wide, and one and a half cubits high. 11 He overlaid it with pure gold and put a gold molding around it. 12 He made a rim one handbreadth wide around it, and made a gold molding around the rim. 13 He cast four gold rings for it and put the rings on the four corners where its four feet were. 14 The rings were close to the rim as holders for the poles to carry the table. 15 He made the poles of acacia wood and overlaid them with gold to carry the table. 16 He made the utensils which were on the table, its plates, dishes, bowls, and jars out of which libations are poured. He made them of pure gold.

The Lamp Stand

17 He made the lamp stand of pure gold. He made the lamp stand, its base, and stem of hammered work and its cups, calyxes, and flowers were of one piece with it. 18 Six branches extended from its sides, three branches of the lamp stand from one side of it, and three branches of the lamp stand from its other side. 19 Three cups shaped like almond blossoms with calyxes and flowers were on one branch and three cups shaped like almond blossoms with calyxes and flowers were on the other branch, and so on for the six branches extending from the lamp stand. 20 On the lamp stand itself there were four cups shaped like almond blossoms each with their calyxes and flowers. 21 A calyx was under the two branches that extended out of the stem; a calyx was under the next pair of branches that extended out of the stem; and a calyx was under the last pair of branches that extended out of the stem, and so on for the six branches extending from the lamp stand. 22 Their calyxes and their branches were of one piece with it, all of it was of one piece of hammered work of pure gold. 23 He made its seven lamps, its tongs, and its trays from pure gold. 24 He made it and all of its furnishings from a talent of pure gold.

The Altar for Incense

25 He made the altar for burning incense of acacia wood, a square, one cubit long, one cubit wide, and two cubits high, with its horns of one piece with it. 26 He overlaid it with pure gold—its top, its sides all around, and its horns—and he made a gold molding around it. 27 He made two gold rings for it under its molding, on its two opposite sides, as holders for poles by which to carry it. 28 He made the poles of acacia wood and overlaid them with gold. 29 And he made the holy anointing oil and the pure aromatic incense, the work of a perfumer. — Exodus 37 | International Standard Version (ISV) The Holy Bible: International Standard Version® Copyright © 1996-2012 The ISV Foundation. All rights reserved internationally. Cross References: Exodus 25:5; Exodus 25:10-11; Exodus 25:17; Exodus 25:27; Exodus 25:31-32; Exodus 25:33-34; Exodus 25:35-36; Exodus 30:1; Exodus 30:23; Exodus 30:25; Exodus 31:7-8; Exodus 37:10; 1 Kings 6:23; 1 Kings 6:27; 1 Kings 8:8; Hebrews 9:4; Hebrews 9:4; Revelation 1:12; Revelation 1:20

Exodus 37 Bible Commentary - Matthew Henry (concise)

Key Passages in Exodus 37

1. The ark and mercy seat with cherubim made 10. The table of showbread with its vessels 17. The candlestick with its lamps and instruments 25. The altar of incense 29. The anointing oil and sweet incense

[nbmudkip]

my team for this event is so funny. one of these things is not like the other

[heartfullofleeches]

i love all my human kids equally. Miller, Calliope, Teddi, Sammy, Ben Erin, Spencer......V-bucks

[lars-canyon]

ISVS (beta) – 12-23-24 – Fennel [Vassago-B] vs Tenkyoken (Dancouga-A)

Vassago's Theme on Central Authority Agency

[allscripture]

Abide in me, and I will abide in you.

John 15:4 (ISV)

[voidishvulture]

Viva taking Gar out to a popular park on Vivoidia, their caffeine juice is extra sweet and their parks extra purple.

[redwinterroses]

hello! I've seen that you play on isv. is that the impulse Patreon server?

It is! Though Impulse is moving most of his support to Glimpse, which is a better option for creators as I understand it (...which, to be clear, is not much). But same reward apply, I believe, and the $10 a month tier and up grants you whitelisting on the server. It's a GREAT community and honestly, while I'm still a huge Impulse fan, I stick around even more for the community these days. XD

[onedigital]

Dynatrace se une a la Asociación de Seguridad Inteligente de Microsoft

Dynatrace se integra con la tecnología de seguridad de Microsoft para mejorar la seguridad en la nube para los clientes Continue reading Dynatrace se une a la Asociación de Seguridad Inteligente de Microsoft

[mybeautifulchristianjourney]

A Prayer for Judging the Wicked

1 Why do you stand far away, Lord? Why do you hide in times of distress? 2 The wicked one arrogantly pursues the afflicted, who are trapped in the schemes he devises. 3 For the wicked one boasts about his own desire; he blesses the greedy and despises the Lord. 4 With haughty arrogance, the wicked thinks, “God will not seek justice.” He always presumes “There is no God.” 5 Their ways always seem prosperous.

Your judgments are on high, far away from them.

They scoff at all their enemies. 6 They say to themselves, “We will not be moved throughout all time, and we will not experience adversity.” 7 Their mouth is full of curses, lies, and oppression, their tongues spread trouble and iniquity. 8 They wait in ambush in the villages, they kill the innocent in secret. 9 Their eyes secretly watch the helpless, lying in wait like a lion in his den. They lie in wait to catch the afflicted. They catch the afflicted when they pull him into their net.

10 The victim is crushed, and he sinks down; the helpless fall by their might. 11 The wicked say to themselves, “God has forgotten, he has hidden his face, he will never see it.”

12 Rise up, Lord! Raise your hand, God. Don’t forget the afflicted! 13 Why do the wicked despise God and say to themselves, “God will not seek justice.”?

14 But you do see! You take note of trouble and grief in order to take the matter into your own hand. The helpless one commits himself to you; you have been the orphan’s helper.

15 Break the arm of the wicked and evil man; so that when you seek out his wickedness you will find it no more. 16 The Lord is king forever and ever; nations will perish from his land.

17 Lord, you heard the desire of the afflicted; you will strengthen them, you will listen carefully, 18 to do justice for the orphan and the oppressed, so that men of the earth may cause terror no more. — Psalm 10 | International Standard Version (ISV) The International Standard Version of the Holy Bible Copyright © 1995-2014 by ISV Foundation. All Rights Reserved internationally. Cross References: Exodus 15:18; Exodus 22:23; Deuteronomy 8:20; 1 Kings 9:3; 1 Chronicles 29:18; Job 20:12; Job 22:13; Job 24:14; Job 38:15; Psalm 1:1; Psalm 7:16; Psalm 9:12; Psalm 13:1; Psalm 14:1; Psalm 17:4; Psalm 17:7; Psalm 17:12; Psalm 22:1; Psalm 22:11; Psalm 28:5; Psalm 30:6; Psalm 36:1-2; Psalm 37:17; Psalm 49:6; Psalm 49:18; Psalm 59:7; Psalm 146:9; Proverbs 24:15; Isaiah 29:15; Isaiah 29:20; Matthew 5:21; Matthew 13:19; Romans 3:14; Revelation 18:7

Commentary on Psalms 10 by Matthew Henry

Key Passages in Psalm 10

[bizkonnect]

Reaching ISVs effectively requires a targeted approach, and this is where actionable org charts come into play. An actionable org chart is more than just a map of who’s who in an organization. It is an account map that provides deep insights into decision-makers and influencers within a company.

[cloudatlasinc]

UnifyCloud recognized as a finalist of 2024 Microsoft Americas Partner of the Year

Redmond, WA, USA — June 27, 2024: UnifyCloud today announced it was named a finalist of ISV Innovation 2024 Microsoft Americas Partner of the Year Award. The company received recognition among a group of top Microsoft partners for demonstrating innovation and successfully delivering customer solutions using Microsoft technologies.

“Being named a Microsoft Americas Partner of the Year Finalist for ISV Innovation is a testament to UnifyCloud’s relentless pursuit of excellence and innovation.” said UnifyCloud CEO Marc Pinotti. “This recognition highlights our commitment to developing an end-to-end automated cloud transformation platform that delivers cutting-edge solutions in cloud migration and artificial intelligence that empowers businesses to achieve their digital transformation goals. We are deeply honored to be acknowledged by Microsoft and the Americas region and look forward to continuing our partnership to deliver exceptional solutions to Microsoft and our partners.”

The Microsoft Americas Partner of the Year Awards acknowledge Microsoft partners who have created and delivered exceptional Microsoft-based solutions, services, and devices in the past year. The award selections are categorized, with honorees selected from a pool of over 2,000 submitted nominations. UnifyCloud was recognized for providing outstanding solutions and services in ISV innovation.

The ISV Innovation Partner of the Year award recognizes ISV Partners who have demonstrated a high level of innovation leveraging Microsoft Cloud advanced services, including AI, introducing new techniques, approaches, or applications that push the boundaries of what is currently possible.

“It is with great excitement that we celebrate the winners and finalists of the 2024 Microsoft Partner of the Year Awards!” said Nina Harding, Corporate Vice President, Americas Global Partner Solutions. “These incredible partners showcased their innovation and collaboration which have fostered customer success, AI and CoPilot activation, and transformed businesses on the Microsoft Cloud.”

The Microsoft Partner of the Year Awards will be announced at the Americas Start for Partners, a digital event, which will take place on July 12th this year. Additional details on the 2024 awards are available on the Americas Partner Blog here: Americas Partner Blog.

About UnifyCloud:

UnifyCloud is a leading provider of cloud migration and optimization solutions, helping organizations simplify and accelerate their journey to the cloud. With a focus on innovation and customer success, UnifyCloud and its CloudAtlas platform empowers organizations to maximize the benefits of cloud computing, minimize complexity and risk, and achieve their strategic objectives in the cloud.

A Microsoft Solutions Partner in the areas of Infrastructure, Digital & App Innovation and Data & AI, the company has been recognized as a Microsoft Partner of the Year honoree for five consecutive years:

2024 Microsoft Worldwide Modernizing Applications Partner of the Year Award finalist

2023 Microsoft Worldwide Modernizing Applications Partner of the Year Award finalist

2022 Microsoft Worldwide Migration to Azure Partner of the Year Award finalist

2021 Microsoft Worldwide Modernizing Applications Partner of the Year Award finalist

2020 Microsoft Worldwide Solution Assessment Partner of the Year Award winner

2023 Microsoft Asia Pacific Region Partner of the Year finalist nominee

Independent Solutions Vendor (ISV)

Digital and App Innovation (Azure)

Infrastructure (Azure)

Social Impact

For additional information contact, marke@unifycloud.com or visit www.unifycloud.com.

[allscripture]

Seek the LORD while he may be found, call upon him while he is near.

Isaiah 55:6 (ISV)

[voidishvulture]

That one meme, Gark thought she was going to rock her world, now she's learning all of Vivas villagers names.

[ibarrau]

Estrategia para licencias PowerBi - Fabric

La popularidad de Fabric no para de extenderse y eso hace que cada vez más aparezcan confusiones y dudas sobre licencias. Cada día llegan más dudas sobre el formato de licencias y como encaja lo nuevo en lo viejo. Dentro de esas dudas aparecen muchas alternativas para manejo de licencias.

En este artículo vamos a hablar de puntos medios y grises para optimizar costos de nuestras licencias encontrando el mejor balance con los nuevos planes que nos ofrece Fabric.

Primero vamos con conocimientos básicos de licencias en este antiguo artículo que escribí. En el mismo vamos a conocer detalles de las licencias disponibles en julio 2024.

Si ya conocen las de PowerBi, lo nuevo es Fabric. Una licencia por capacidad que viene a expandir los artefactos o contenidos que podemos crear dentro de un área de trabajo. Sus planes inician con valores más económicos que las capacidades anteriores, lo que permiten que todo tipo de organización pueda acceder al uso de éstos artefactos. Sin embargo, el uso de los tradicionales contenidos de PowerBi siguen bajo el mismo esquema.

La estrategía de optimización se base específicamente en los usuarios. Si tenemos capacidades dedicadas... ¿Por qué pagamos licencias por usuarios? esta es la pregunta que trae el principal contexto y razón del artículo. A las organizaciones les cuesta este concepto, más aún viendo que los contenidos de Fabric no necesitan licencias de usuario. No necesitamos una licencia PRO para desarrollar un notebook, escribir en Onelake o consultar un warehouse con SQL. Para resolver esta paradoja vamos a dividir nuestro enfoque en los dos tipos de usuarios, desarrolladores y visores.

Enfoque de Visores

Algo que suele trae mucho dolor a organizaciones que usan PowerBi es que los visores en entornos de capacidad compartida (pro o ppu), tengan que pagar licencia. Uno puede pensar que pagando una "Capacidad Dedicada" como premium lo soluciona, sin embargo premium va a desaparecer y quedará Fabric. Muchos podrán pensar que esta es la solución definitiva, puesto que Fabric comienza con planes muy económicos, pero no es cierto. La característica de compartir con usuarios gratuitos comienza en un plan F64, cuyo costo ronda entre 5000 y 8000 dolares (dependiendo el tipo de pago). Lo que nos hace pensar que valdría la pena si nuestra operación interna cuenta con más de 500 usuarios visores de PowerBi (puesto que una licencia pro sale 10 dolares). Ciertamente, un número que solo grandes empresas pueden considerar.

Entonces, ¿Qué hacemos cuando no podemos pagar ese monto? Si podemos comprar capacidades dedicadas más chicas, ¿Cómo podríamos compartir a usuarios visores sin pagarles licencias Pro? La respuesta es una característica bastante olvidada en el entorno de analytics. Estoy hablando de la feature de "Embedded". PowerBi cuenta con una compleja pero poderosa posibilidad de embeber informes en aplicaciones web con grandes posibilidades. Una de esas posibilidades es delegar la seguridad y loguear a la aplicación que refleja los informes. De ese modo, podríamos compartir a todos los usuarios visores que querramos sin pagar licencias. Sin embargo, no es tan simple puesto que necesitaríamos un potente equipo de desarrollo que construya esta web app aprendiendo todos los enfoques de power bi con especial atención a la seguridad, dado que ahora es responsabilidad nuestra (nos la delega microsoft al usar embedded).

Si no tenemos equipo de desarrollo y queremos aprovechar esa capacidad. ¿Cómo lo resolvemos?. La opción más viable sería comprando un producto de un tercero. Varias instituciones proveen este tipo de software. Por ejemplo, una que conozco en español es PiBi. PiBi es una plataforma web como servicio (SaaS) que usa la característica de Power Bi Embedded.  Una construcción que interactúa con tu entorno de Azure y te permite distribuir informes de PowerBi de manera segura, simple y eficiente.

¿Qué ventajas encontramos si nos embarcamos en este camino?

Operación de informes en un solo lugar

Más sencillo de usar que Fabric/PowerBi Service

Compartir con usuarios externos a la organización

Logins SSO Google/Microsoft

Mantener seguridad y privacidad

El requerimiento para usar Embedded es tener una licencia por capacidad. Herramientas como ésts pueden partir de valores como 450 dolares por mes, que junto a una licencia básica de Fabric con pago anual de 150 dolares son 600 dolares. Si nuestra operación de usuarios internos ronda entre 60 y 500 usuarios, encaja perfectamente para optimizar nuestra estrategia de Power Bi. Por supuesto, que habría detalles como si tenemos modelos y mucho volumen de datos, puede que necesitemos un Fabric un poco más elevado, pero deberíamos pensar a ese como costo de almacenamiento y no de distribución de contenido a los usuarios.

Enfoque de desarrolladores

En la mayoría de los casos, lo primero que normalmente tendería a evolucionar, son los visores. Una vez encontrado un punto de madurez en ellos, seguirá esta propuesta. Esto quiere decir que lo más probable es que YA contemos con capacidad dedicada (para usar la feature embedded). Pero no desesperen si no la tienen, esta estretegia es totalmente viable sin capacidad tal como lo explico en este otro artículo. Las estrategias no estan ligadas una a otra, aunque son poderosas juntas.

El eje para liberar a los usuarios desarrolladores de sus licencias es pensar en desarrollo de software convencional. Si pensamos en la industra de software, un desarrollador, sea backend o frontend, tiene como trabajo solamente desarrollar. Su eje y foco esta en construir. Hoy esos roles no hacen integración de soluciones, implementaciones o deploys, puestas en producción, etc. Existen roles como DevOps que ayudan a delegar la construcción final.

Tomando este enfoque como guía, si queremos que los desarrolladores de PowerBi no usen licencias, debemos concentrarnos en lo básico, un repositorio. Hoy Fabric nos da la posibilidad de integrar repositorios de GIT con Áreas de Trabajo. Esto no solo nos ayuda a que el desarrollador ni piense en Fabric o PowerBi Service, sino que también almacena los desarrollos en formato Power Bi Project que nos deja mergear código. Si queremos ver eso en más profundidad pueden abrir éste artículo.

Así los desarrolladores de Power Bi. Solo desarrollarán. Comienzan el día armando o con un pull a su branch de repositorio, comiteando cambios y al terminar un push. Ni piensa ni escucha quienes ven que informes y donde está. Luego podemos pensar en otro perfil que podemos decirle Admin del Area o DataOps que garantice que los reportes están en el lugar apropiado o sean automáticamente deployados. Veamos un poco más gráfico esto:

Vean como Local Machine nunca ve Fabric. El desarrollador no necesita ingresar al portal web. Solo necesitamos licencias para DataOps o Administradores de areas. Así es como reducimos licencias y ganamos robustez y soluciones tanto versionables como escalables.

Se que fue mucho texto pero espero que haya sido a meno y les traigan nuevas ideas para optimizar efectivamente la operación y licencias de sus entornos.